When trying to run a simple "Hello world" D lang code snippet in Visual Studio (using the visual-d plugin), I see the following error in the logs:
D:\mydata\ConsoleApp\ConsoleApp\Debug\ConsoleApp.pdb: cannot load PDB helper DLL
where ConsoleApp is the name of my app. As per this thread, the problem should have been fixed in the v0.3.38-1 installer but I still see this issue. I'm using Windows 8.1 with Visual Studio Standalone/Integrated Shell.
Any help is making this run would be much appreciated.
If the latest VisualD installed does not fix the problem, then try the following fix http://stuff.benjamin-thaut.de/D/visualdfix.reg by Benjamin Thaut. Here is what what he wrote on the NG: "This is for visual studio 2010. If you need it for a
different version you have to open it with a text editor and change
"10.0" to "11.0" for 2012 and "12.0" for 2013."
I switched to the Mago debugger as mentioned on this wiki page and the error went away. Since I just want to get a feel of the language, not using the "native" debugging format doesn't bother me a lot, so all is well now.
Related
I'm trying to migrate from VS2012 to VS2015. I have a need to edit Classic ASP code.
The code opens just fine in VS2012. It will not open in VS2015. Or, more accurately, when I open it in VS2015, I don't see any code; all I see is a tab with the file name and a big blank blue field where the code should be.
What do I need to set in order to view it? I can't seem to find this anywhere.
Thanks in advance...
have you tried reinstalling VS? I'm running VS2017 without any problems, having just upgraded from VS2015, which I ran without issues as well. I'd try a reinstall and see if that resolves the problem.
I recently installed Visual Studio 2013 Ultimate version on my machine. I'm just trying to create a sample windows form project and trying to open the designer / form by double clicking on Form1.cs and I'm getting this weird error message:
"the service microsoft.visualstudio.shell.interop.iselectioncontainer already exists in the service container"
My system is already having Visual Studio 2010 which is working smoothly from a long time. I then installed Visual Studio 2012 which was giving the same problem as above. So I went ahead with installing VS 2013 hoping that I might be able to get rid of this issue, but no use.
Once I click OK on the error windows, I can see the following "message" in the bottom Error List window:
"The file 'C:\Users\ABCD\Documents\Visual Studio 2013\Projects\WebSite1\WindowsFormsApplication1\Form1.cs' does not support code parsing or generation because it is not contained within a project that supports code."
I have spent 2-3 days searching various blogs like these, all of which talk about previous version of Visual Studio like VS 2005 / VS 2008:
https://connect.microsoft.com/VisualStudio/feedback/details/311949/the-service-microsoft-visualstudio-shell-interop-iselectioncontainer-already-exists-in-the-service-container
Form inheritance in Visual Studio 2008 doesn't work
I have even tried uninstalling and reinstalling VS 2013, again no use.
It would be really great if someone can help me out in fixing this.
I've just had the exact same error message.
After compiling the solution(F6 or Build->Build Solution) it worked fine for me.
To deal with your issue, please first make sure that you installed latest updates on your Windows 8 machine, and then repair VS2013.
During your repairing process, please temporally turn off your anti-virus/antispyware software and repair VS2013 with the Administrator privilege.
follow this link
The problem got resolved finally, after so many days and various frustrating tries to resolve the issue. I should thank Tim Atkins from Microsoft for helping me with resolving this issue.
Fix: When we tried 'gacutil /l system.design', we found that there were 3 variants of system.design; One from .Net 2.0 targetting MSIL, second from .Net 4.0 targetting x86 and last one also from .Net 4.0, but targetting MSIL.
On a working machine, there were only 2 entries, the .Net 4.0 one targetting x86 wasn't there. Hence we uninstalled this version using gacutil which did the magic. I was so relieved seeing the win forms popping up without any errors anymore :)
I changed the target framework from 4.5 to 4.6.1 and it fixed it for me. My assumption is sometimes when you change target framework back and forth and the process does not go through all the way (cancelling in the middle of changing it) - something happens that leads to this error. Hope that helps
I solved this be closing VS, deleting contents of the .vs folder where my solution is, restarting VS and recompiling.
Seems like one of those file/settings/caching problems that pop up now and then, might be after switching source branch.
VS2019, .net fw 4.6.2.
If your C drive (Where you are installing Visual Studio) does not have enough space, try moving some files from the C drive to another drives.
I've just attempted to use Firebreath and have followed their video tutorial for Windows and come across the error that says:
Check for working C compiler using Visual Studio 10 -- broken
And then says:
It fails with following output:
Change Dir:
And then lists the drive. This happens when running prep2010.cmd. I have found a post about it, but the forums won't let me log in and there is no answer. It's here: http://forum.firebreath.org/topic/274/?page=1#post-1117 and is exactly the same error, I believe. The last post talks about running prep2010 from inside the vs2010 command shell. What does that mean?
Has anyone else had this error or know how it is caused? I have no idea how to approach it.
Thankyou
I know this is really old.. but in case someone else has this problem, the solution for me was to install service pack 1 for visual studio 2010
As I said in the comment above, this is not "FireBreath" that is saying your compiler is broken; the prep command uses CMake to generate the project files, and it is from cmake that the error comes.
In your start menu where Visual Studio 2010 is there should be a "tools" or "utilities" subfolder and in there somewhere there is a "Visual Studio 2010 Command Prompt" link. That starts a command prompt with environment variables and path set up so that the vs2010 commands are all available. The error you're seeing is indicating that for whatever reason, CMake is unable to find visual studio 2010.
I don't know if using the vs2010 command prompt will help or not; it doesn't have any trouble finding vs2010 on any of my boxes. I can postulate that perhaps if you installed it to a nonstandard location, in a nonstandard way, or your registry got screwed up any of these things could potentially cause the issue that you are seeing. Also if you don't have vs2010 installed it would certainly cause this issue =]
I'd recommend first trying the vs2010 command prompt; if that doesn't work, you may have to try uninstalling and reinstalling vs2010. If that doesn't work, I'm out of ideas, and maybe someone who knows more about cmake will have a suggestion :-(
Service pack 1:
http://www.microsoft.com/en-us/download/details.aspx?id=23691
Configure cmake with generator: MSVC2010 x64
I also had MSCV 2010 x64 on windows 7 and installing service pack one also helped.
Also make sure that all your external dependancies are (x64) versions:
MSVC version:
http://visual-studio-2010.en.malavida.com/
Gl&HF
Surely the answer will be "you can't" or "use XP mode", but I'd like to know if it it possible.
The issue I have is that whenever I debug some application and hit a breakpoint, when I stop the debugger the debuggee remains stuck. It can't be killed, I can't attach another debugger (it says it is already being debugged). It won't go away until I close Visual C++.
This is hapenning on a Windows 7 64 bits install. VC has SP 6 installed.
My previous fix was horrible.
Finally, I developped a new fix, working perfectly with the english version of Visual Studio 6. (SP6 I think)
You need to check the version of the file DM.dll located into "Common/MSDev98/Bin"
The correct version is 6.0.9782.0.
link: http://www.dr-hoiby.com/TLLOC.dll (28KB)
how to install: replace "Common/MSDev98/Bin/TLLOC.dll" by the version downloaded.
Best regards.
Comment reposted:
You can try using Visual Studio 2008 with VC6 compiler. I recently blogged about this.
I developped a little fix for that.
You just have to copy the file "ShiftF5Fix.dll" into "Common/MSDev98/AddIns/" et load it from Visual.
It's an hugly fix.
If you modify your source file during debugging you have you answer "NO" to the poup displayed after you press "SHIFT+F5" to stop the process.
link : http://www.dr-hoiby.com/ShiftF5Fix.dll
Best regards
Another option would be to install daffodil.
This is an open source project to compile all versions of visual studio in VS2010.
Once this is configured you can use visual studio 2010 debugger to debug VC6 projects.
On the heels of Dr Holby, I implemented a leaner variant, with source code:
http://www.algonet.se/~tamlin/TLLOC_fixer.zip
The code currently only understands sp4 (?) and SP6, but I think it'll cover most cases.
You only need to compile the source (1.cpp, 1.rc), rename your existing TLLOC.DLL (which btw stands for Transport Layer Local - as opposed to remote debugging) to TLLOC.old.dll, and drop in the one you compiled (~4KB). Should work like a charm for all 32-bit debugging needs, from Windows 95 to Windows 7 (and later).
I'm trying to open a silverlight project in Visual Studio 2008 and getting this error.
The project type is not supported by this installation.
Let me tell you I did installed:
VS2008
SP1
Silverlight Tools 3
Silverlight SDK
Silverlight
And they were installed in the sequence they are mentioned here. Still I'm getting the same error.
Adding some more details which might be helpful in identifying the cause:
When I try to create a new silverlight project it gives me error "Object reference not set to an instance of an object". And shows "...project creation failed."
I tried unistalling all of the things and installing them again. It really took a lot of time but didn't solved my problem.
Any help appreciated.
Open the project.csproj file with another editor, delete whatever you find between
<ProjectTypeGuids></ProjectTypeGuids>
I've had the same error when I tried to open a solution which required VB.NET, despite everything (to my knowledge) being C#.
If you've done a full install of VS then try this solution: http://andrewgunn.blogspot.com/2008/03/silverlight-project-type-is-not.html
Let us know how it goes.
Do you know who the silverlight project was created by? If so, then contact them and ask them if they used VS 2008 or if they used VS 2010 beta 1/2 (VS 2010 has a lot more and better support for silverlight so it's probable)
If they used VS 2010, then just go to the microsoft website and download you a copy... it's free(right now)
(and if you'll be doing much silverlight development, I'd recommend downloading it anyway. It has code completion for XAML!)
run devenv /setup