I'm writing a project in Visual Basic 2008 Express Edition, which used to work completely fine until that moment, when I decided to install MS Chart Control in order to create a diagram in my project.
This didn't work (error "failed to register activex control" when dragging the tool into the form; although I registered everything successfully as an administrator) and many hours googling myself through forums made it clear to me, that this seems to be a general bug. At least I couldn't find a solution.
So now, I removed the tool MS Chart Control again, but still, I get error messages, when I build my project. After reinstalling Visual Basic 2008 Express Edition completely and removing all references that pointed on the MS Chart Library, I managed to delete some of them.
However three errors still remain, when I build the project. All of them of the same kind:
"Cannot write to the output file "C:...\Visual Studio 2008\Projects\Test\Test\obj\Debug\Test.Form1.resources".
Access to the path 'C:...\Visual Studio 2008\Projects\Test\Test\obj\Debug\Test.Form1.resources' is denied."
(same thing with two other files in the Debug-folder)
I again spent several hours searching through forums, but could not find a helpful answer. I already tried reinstalling everything again as well as rebooting windows and emptying the bin.
I also made sure, that the folder properties of 'Debug' are set on 'full access'.
Still, Visual Basic can not write on these files anymore.
I would be very grateful for any answer. Please note, that I am not an expert, neither on programming nor on computer-troubleshooting, so I would be happy about generally understandable (step-by-step) answers.
Many thanks in advance!
Regards,
c.
I just found out, that it works, if I open Visual Basic Studio as an administrator.
Strange, because a month ago, it always worked fine and I don't think I have changed anything about the folder or datas properties.
Anyway.... that solved the problem, I guess.
Related
I am not sure how this came to be exactly, but as of today I can't build anything at all in Visual Studio 2015 (community edition).
Even when creating a brand new project, console, winforms, class lib makes no difference, all I get when I try to build is the infamous "The operation could not be completed" popup. I have tried disabling the visual studio hosting process in the project properties, but to no avail.
It's really frustrating since I can't actually work on any projects at all right now. It feels like this should be a well-known issue, but searching here and on google only gives vaguely similar results but I can't find anything matching fully.
Please advise if I can access an error log or something like that to give more info.
I have tried to create a package for a VSTO addin using windows installer in Visual Studio 2013 but having no success. By that I mean I can create a exe and msi by using the Visual Studio Installer Setup Wizard and selecting everything as default, which seems to all run ok when installed but I don't get my addin appear anywhere in Word (I have looked in File-Options-Addins- com addins/dissabled addins).
I have spent quite a lot of time googling to find some instructions but with no success. Can anyone please help me by either writting some instuctions on here or pointing me to a link where someone has already done it?
Can I point out, I know how to create a package using Installsheild instead but I was having a few issues with that, so wanted to try this instead. So please don't suggest that as an approach, or wix.
You don't mention which version of Word you're using. Traditionally, this has been a nightmare - but I would guess that the most horrible things has been fixed in more recent versions of Office. In particular I'm thinking of the "KB908002" which had to be applied during setup (don't know if that is the case still).
One thing that may be forgotten is that you are required to install the "Microsoft Primary Interop Assemblies" (PIA) on the target machine, and that you have to apply the correct PIA depending on which version of Office you have on the target machine.
Anyway, this article http://blogs.msdn.com/b/vsod/archive/2008/04/22/troubleshooting-com-add-in-load-failures.aspx will give you quite a few ideas. Specifically, enabling the Fusion logging which has help me way back.
Good luck!
My solution currently contains 20 projects in total. These are all window
applications.
But lately after my OS(Windows XP SP3) downloaded updates from Microsoft and after adding just one window form in one of the projects, VS 2003 IDE starts crashing when trying to debug the solution. After crashing VS needs to be reinstall....
ANY advice that might save me from having to reinstall VS2003 over and over?thanks.
I'd disable all addons you might have installed and see if that helps (VS is usually quite stable, but some addons are not). If so, re-enable them one by one to find which one causes the problem
If that doesn't help, see if you can re-create the crash with a minimal solution, and if you can, it might be worth talking with MS about it, their Connect website might be a good place to start.
Please note, if you edit your question to give more specific information (VS version & edition, what projects you're using etc) someone might be able to give a more specific answer, but I think with that generic question, you'll only get generic answers.
When I try to start my visual basic to open a project it doesnt seem to be working and keep prompting a error 'VB6EXT.OLB' could not be register. What does that mean? Need helps on this matter, thanks
Just Right Click on VB6.exe and CLick On Run As Administrator..
Hope It works
VBE6EXT.OLB is the Visual Basic for Applications Extensibility Library. That filename seems to indicate that you're dealing with version 5.3, which apparently shipped with Microsoft Office 2000. It would seem your VB6 project is an Office Automation project then?
Google turns up the following links, which may be helpful:
BUG: Interface methods in the VBA Extensibility Library (VBE) are changed
PRB: Visual Studio Setup program may include Office OLB files in setup list
Neither seems to directly answer your question, but they seem like a good place to start.
Since Visual Basic 6 (and Microsoft Office 2000 as well) hit end-of-life well before Windows Vista was released, there may be a fundamental conflict between them. You might be better off trying to develop your application on an older version of Windows.
This just happened to me (literally seconds ago) and I came HERE first stop.
I was looking for THE answer. As it happened, MS-Office 2010 offered to repair the problem...
... and, skeptically, I accepted.
To my astonishment I was soon greeted by my FAVOURITE splash screen in the world - I've got my Rubberduck
Anyway, I'm relieved the Auto Fix worked...
Visual C++ doens't work on my Vista. both 2010 and 2008 fails to create new projects. what alternative do i have ? I am sick of googling and trying out all the other hacks to fix it.
What other alternatives? If you're tired of trying the "hacks", I'd be looking at one or more of the following, in no particular order.
Use a different IDE.
Re-install Visual Studio.
Re-install Windows along with all your other apps (including VS).
Try installing Visual Studio in a newly created virtual machine.
Upgrade to XP :-)
Raise a support call with Microsoft.
Hire someone to fix the problem for you.
Provide more detail in this question.
Really, the possibilities are (figuratively) endless. There are any number of problems that could be causing this and the detail is a bit light on at the moment. What I tend to do is always have a fresh-install VM of XP lying around so I can test problems in environments that haven't been heavily changed from the originals.
No doubt we will be able to provide more help once the problem has been narrowed down some more. Sorry I can't help more than that at the moment.
I might guess that you are having trouble creating the projects because you don't have permission to the folder where you're trying to write them. Try right clicking on Visual Studio and saying 'Run as Administrator' then create the project.
You could use DevC++ or Eclipse as the compiler perhaps.