in visual studio 2013 vb.net coding, when you click 'Start' and it gives you a popup message saying that it contains errors would you like to run the last successful build?
How can I really get back the code of the last successful build because I have done several changes and I really want the old runnable build back.
I really appreciate all the help I can get.
thanks in advance!
As Karen advised, if your code isnt under version control, and you dont have backups (or undo history), then the code is gone.
One option, if you are desperate to see the content of the assembly, may be to reflect it. This is the process of turning the assembly from IL back in to source. The code that is produced will not be a mirror image of the original, as it will have been optimized/shuffled by the compiler, but it is often enough. If you are interested check out dnSpy.
Related
I made some changes to a VB.Net website project in Visual Studio 2019, and then I merged them into the UAT project in TFS, so that they can be published to our UAT site. When I try to build the project the Error List contains one item stating:
Maximum number of errors has been exceeded.
When I look at the Output tab I can see a long list of errors, but when I investigate them they are not errors at all. Some of the messages indicate syntax errors, but when I view the code nothing is highlighted and it all looks fine. Some of them say that a variable has not been declared, but it has. I also get Character is not valid errors - but again nothing is highlighted.
I should say that none of these errors is in any of the files I have been working on so they should be the same as the code which works fine on the UAT site. I already tried deleting the .vs folder and removing related folders from the Temporary ASP.Net Files folder, which fixed some issues I was having earlier, but not these errors.
I don't want to rant, but I feel like if Microsoft had a better testing regime there would be less of these sorts of issues and developers wouldn't need to waste so much time trying to work around their mistakes. I'm completely stuck at the moment so any suggestions would be gratefully received.
I wish I could say I know how to fix this but I don't. All I know is after a mixture of visual studio restarts, failed publishes, and a couple of fixed references the project now compiles and even publishes.
That would've been a lot easier and less stressful if visual studio provided more accurate error messages
I am working with visual studio 2012, and my problem occurs in a large, old winforms application solution when I try to compile the whole application (dozens of projects).
When I get the latest code from source control (Team Foundation Server) for the first time, and build the solution, it builds just fine the first time. Then, if I make any changes, a later Build/Rebuild, will sometimes (not always) result in lots of projects in the solution throwing the following error for some of its resx files.
Unable to create a manifest resource name for "Contracts\Templates\ContractTemplateDb.resx". Could not find a part of the path 'C:\Windows\system32\Contracts\Templates\ContractTemplateDb.vb'
OR
Invalid Resx file. Could not find a part of the path 'C:\Windows\system32\NeptuneForms\HelpForm.resx'.
The problem is that there is no reason it should be looking in C:\Windows\system32 for these files, as they exist fine (and did during the last build) in the local directory of the project! The random directory is not always C:\Windows\system32, sometimes it is a random directory of another project, or even in another branch.
This happens sporadically to some of our developers, frequently to others, and almost always to me, and it seems unrelated to the code we are writing, because when it happened, I rolled back all the changes we had made since it started happening, and it still happened.
There are two things I've tried, that had no success.
Recreate the entire solution, and remove and readd all resource files as though they never existed before.
Install all windows updates and get the latest updates to Visual Studio 2012
Nothing has helped, and I am at a loss. My next step is to upgrade to 2013 and hope for the best, but I'm afraid thats not going to help either.
Does anyone have any similar experience, or any ideas of other things to try? I'm pulling my hair out over this one...
Having a very odd issue with Visual Studio 2013, curious if anyone else is seeing anything similar. I have VS 2013 Ultimate, it seems like once a day, while I'm working with a file, the compiler just suddenly freaks out and doesn't detect my code anymore in my web forms. Take a look at the screenshot below (I just chose a random spot in the middle of the web form), but out of nowhere, VS starts erroring, telling me that variables aren't declared, that method arguments need parenthesis on lines of code that aren't methods, all sorts of whacky stuff.
I assure you, I don't have any broken references, I didn't forget to close an if statement.. nothing like that. All I'm doing it writing some code, and randomly the whole page just starts to error like this. To resolve, all I can do is copy the code contents, delete the page, recreate the page, and paste the contents back into my "new" file... same exact code, only no errors. I wouldn't even worry about doing this if I wasn't doing this at least once a day.
Any help is appreciated, thanks!
Edit: For what it's worth, I found a slightly easier workaround for this issue. If I edit the properties of the class file to "Do not Compile" and then back to "Compile", the IDE is able to read the file just fine...
It looks like this is simply a bug in the Vb.Net Compiler / IDE. I agree it's unlikely to be a bug in your code because you can see that the error squiggles don't line up with places that would represent the errors you are reporting. This is sometimes a sign of an IDE bug
In terms of fixing the problem though you can probably get them to go away by closing and reopening the solution in question. Baring that restarting Visual Studio. I wouldn't resort to deleted / recreating the page.
Long term though you may want to file an issue on connect so the IDE team can try and fix the problem.
http://connect.microsoft.com/VisualStudio
I'm kind of new to Visual Studio. I've built a few simple programs in it, but now I'm in the process of rewriting a huge system I wrote in VBA. What is frustrating me is the Error List in VS is only listing errors for one .vb File in my project, lets call that VBFile1. Now, when I work on another vb File, VBFile2, which is in the same project as VBFile1 no red squiggles or errors are listed for VBFile2. I don't understand how this could happen. This is what I've tried/checked:
Filter is set to 'Current Project' and I played around with the other Filter settings but no change.
Checked the Text Editor under Options and according to the research that I've already done it is fine. Plus, I have never changed any of these settings anyway.
Closed and re-opened Visual Studio.
Closed all open files in the Project and still displays the same error list
Close all files except the VBFile2 but still shows the same error list of VBFile1.
I have Visual Studio 2012 Ultimate. I feel like this should be an easy fix...I just am really confused what's going on.
Hope this makes sense!
UPDATE: Excluded from project, VBFile1 and finally errors are listed for VBFile2...why would this be?
I am not sure if it has been fixed in Visual Studio 2012, but there is a Connect Request for Visual Studio 2010 with a resolution of won't fix because of performance issues. The effect your are seeing is because you have exceeded the maximum number of errors for that project (what I am used to seeing is 102 as the threshold), it will not show you anymore till you fix the ones that it has already shown you.
According to this MSDN article, which I found through this SO question the limitation is still there for the IDE but has been removed for the command line compiler.
From above MSDN Link:
Limitless (Command-line) Errors!
This is actually a good thing, let me explain. For performance reasons, the Visual Basic IDE maxes out at 101 errors (with error #102 being “Maximum number of errors exceeded.”) This can make it difficult to estimate the amount of work remaining in certain situations, particularly in upgrade scenarios. We have removed this limit from the command-line compiler in this release, though it still there in the IDE. What this means is if you want to know exactly how many errors there are for a project, just invoke the compiler through msbuild.exe or vbc.exe and you’ll get your answer.
I realize this question has been asked before, but I was not able to find anything that worked for me yet.
Things I have tried:
Switched settings back to default (mulitple ways)
Project Builds/Compiles fine
Closed VS and restarted
The only thing I haven't been able to try is deleting the ".ncb" file, but that's only because I can't find it. In fact not a single one of all our projects have such a file!
So the first question is why can't I find this file in the solution's root directory? The only file I have there besides the .sln is the .suo.
Then if that doesn't work what other options do I have short of un-installing and re-installing?
As for how it happened this might help. While using VS2008 and VSS6.0 (yuck) I made a number of changes to a lot of files via Find&Replace that I didn't mean to(had Entire Solution selected instead of current document). To undo the changes I exited without saving, reopened the solution, then Undid checkout. After that I lost intellisense! I can't imaging how they're related but it might help.
Thanks,
Jeff
IntelliSense usually stops working when it can't compile correctly. Try a new simple project from scratch and see if it works, if it does you have your answer.
Is this for C++ code? If it is, my suggestion is not to try fixing built-in IntelliSense at all, rather try some 3rd party replacement. My favourite is definitely Visual Assist X, which is lot more robust (it almost never stops working, and it is able to parse even very complicated templated and preprocessed stuff, which often makes IntelliSense "lost".
Visual Assist works with other languages including Visual Basic, however this is something I have no practical experience with. Still, there is a free trial - you may try it, I expect it will be superior to IntelliSense even for VB.
Answer:
I figured out how to fix it. Apparently while I was undoing those changes I somehow excluded the file that I wasn't getting intellisense in from the project.
I just right-clicked on it and said "Include in Project" and viola! Intellisense worked again.
Sorry for the false alarm but I appreciate the effort.
Jeff