Actually quite a simple issue. I have been using a slow laptop to develop on VS2012, and I setup a screamer to develop on now. No change in versions, etc., just doing it all on a different machine.
To be honest, I haven't even copied the Projects folder yet, as I'm not sure if there wold be project-specific options that would be reset/broken.
To be clear, the new 2012 is Ultimate, and I haven't even tried to migrate. There have been a LOT of options/features added to my existing projects & solutions, so it may not be as simple as copy/paste the Projects folder.
What are your thoughts?
#Peter and #JohnnyHK,
You both were right. I was putting this off on a new machine for fear that I'd need to remember a ton of things I hadn't documented in the Solution (and projects under it-about 20).
So I was already using subversion on the old machine, so I added VisualSVN/Tortoise and checked out a copy of the solution to the new Projects folder. There were like 350 errors & more warnings! Yikes!
But I went through them very quickly and it is clean now. One thing that I noticed in the process was that VS2012 is a little 'broken' when it comes to project (on-web) references. NuGet was actually amazing in that as soon as I fired up the Package Console, it went along, finding & installing all the packages & dependencies! :)
I enabled Show All Files, then opened the References tree node, and noted the ones with little yellow "X"s next to them. In the good side, ones that were not needed (I added them, but created just clutter) were good to see & delete. BUT, there were mostly errors from references that had references to DLLs that were actually in the right place, and when I left clicked on the reference with the error icon, the error would simply go away. Weird, but preferable...
The strangest ones were reference to DLLs that were where they were supposed to be (I'd make a .\lib directory in the project, a la *NIX style, and throw all DLLs for that project in there), BUT I had to delete the reference in error (even though the project was pointing to the right file/location) and then re-browse for it, adding it again, and all errors went away.
All in all, I was pretty impressed with the ease-even with the weirdness-it went. Once I saw how the references were broken, I just went into each project & treated each one. Let me be clear for anyone doing a mass WPF migration: If I had started with the first project and worked to the end one, and ONLY fixed the References issues, I would have been done in 5 minutes-includes time for NuGet to auto-load.
I will not lie; This was the first big migration of a solution to a new machine, and when I saw like 700 warnings/errors, I thought "There goes another weekend!", but I will warn those in this situation to NOT go into source code and try to fix each red underline. You will break things!
Related
I am relatively new to Godot, and have started a roguelike game project with a few friends of mine. Recently, we decided to change the repository, in an attempt to add room for newer projects and more people.
After the transition over, files are no longer showing in the Godot file explorer.
I have tried changing the code in the .gd files using notepad and recloning the new repository. I do not think it is an issue with the files themselves, though, as my friend is running the same code without any issues.
We have the same Godot version (3.4.4), code, and both moved over at the same time. I'm still relatively new to Godot, so this may be something obvious I'm missing, but nothing online is helping.
I feel like I'm going crazy, but since updating to the new version of Android Studio, I can no longer tell which files have errors in them.
Previously, if I made a change in one class, like to a method signature, then all other classes that were calling that method would suddenly be highlighted in red (at that section along the top that shows the path). Now it shows nothing as though my code is good, except when I go to compile, I now get a load of errors in the build tab at the bottom, in a really unhelpful way to navigate through.
Is this something I can switch back to through a setting somewhere? I'm really not sure what to search for, but I've been through almost all of them.
UPDATE :
Following another SO post, I turned on and off PowerSave mode, at the bottom of File menu (in Android Studio). This, temporarily at least, seems to have solved things.
This may be what you are looking for?
Either that or it may be in preferences.
I have this issue that I've been spending too much time on.
Working on Visual Studio 2012, on a Windows Phone 8 app, using MVVM Light.
It's a Compile issue that just arose out of the blue. My XAML files are now invalid - but just the XAML files where I try to refer to my ViewModels (event handlers bound to buttons, etc), and the reason for that originates from my App.xaml, where it doesn't see Locator in my myapp.ViewModel namespace, so Locator is now thus seen as invalid.
I've even restored old files from a previous backup from 2 weeks ago, (after copying current files somewhere of course), and the problem still exists. Even just 2 days ago, my app is compiling great.
( btw specifically, when I say Restore, I'm only talking about restoring the subdirectory that contains all of the individual projects, under the Solution directory )
I've tried doing a Git diff, but I only commit xaml's, and cs files, so it didn't show any of my own errors that would cause this.
This seems like some problem with corruption, possibly in a V.S. binary file that I can't see, and I see myself spinning wheels, and not knowing what code to paste her in stackoverflow.
At what point do you just say : "Let's just create a brand new solution " ?
I'd hate to do that, and then the same thing happens again though next week.
However, I'm moving toward a philosophy which says: "dude, get used to doing a re-do, since this stuff happens". (I'm going to just write a Checklist for how to create a solution from new, with all the packages I need, so it's not such a bummer to start fresh.)
This is really frustrating, I am using Visual Studio 2012 for C++ for a project, and it worked fine for a while. Then out of the blue, it started having problems.
The build function does not update the project anymore. I need to do a REBUILD every time I modify anything in my project.
I have looked all over for a solution, but none helped. First of all, I didn't change any settings, but I looked anyway. Tools/Options/Build&Run, Project/Config Manager, you name it I have checked it. It doesn't look like it's a settings problem.
Another thing though, on other forums, I have read that this MIGHT be because of a bad include, that the file included is not there anymore, or something like that. But that is not possible either since I didn't delete any file from the project. But, this problem seems more plausible since, the project at a much earlier stage, had less includes, and it still works.
So, can you help me solve this problem? It is really annoying since most of the solutions out there are NOT working!
Whenever I have run into an issue like this it is usually something like missing project dependencies. You may want to take a look at "Build Solution" not working in Visual C++ anymore. If you are able to share your solution someone may be able to take a look at it.
I have a solution with many projects. This is actually a solution that contains a mix of class libraries and various web applications. It seems that if my colleague makes a change to one of the web projects (or if I do) and then check it in. And then when either one of us gets the latest version project references become broken. They still appear in the references section with no indication of an error, but when you try to compile it cannot see the libraries.
To solve this I have to remove the references and add them back in. Any ideas on what may cause this problem?
Make sure that the paths are relocatable, that you both have the same paths on your PCs (i.e. that you have not used TFS workspace mappings to put different folders in different places), and that you don't move projects around or rename folders etc.
Even when everything is clean and tidy, Visual Studio will occasionally decide it can't find a file that's right under its nose, or that a file somewhere else on your system looks prettier, and it will break the reference. You just have to delete and recreate it in this case. But this usually happens once a month in a team of 10-20 people, and should not occur every time you check in.