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.
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...
Is it safe to use the beta versions of Visual Studio?
By safe I mean, while developing any project in this studio, is it probable that it may cause some losses to my project? Or any other kind of risk?
Should I just use the studio 2008 and
wait for the stable version of Studio
2010?
Purpose of the question: I am doing my graduation project in .NET framework (includes - C#, WPF etc.).So I don't want to put my project at any risk because of some issue regarding (beta) visual studio.Hence the question.
As long as you are using a version control system, there should be no problem. Simply check out your project (or better yet, create a vs2010 branch) to an experimental folder and work from there.
There are no hidden risks when you use version control appropriately.
Visual Studio 2010 will convert your project files to its new format, meaning you'll have trouble if you want to go back to VS2008 later. I'd suggest holding off for now unless you can find a way to keep both old and new versions of the project files up to date.
There's always a risk in using beta software (but then again, there's always a risk in using any software). The whole reason it's called beta is because the company is not confident that it's got all the bugs worked out. Otherwise, it would have been released so they could start raking in the moola.
There are quite a few ways to mitigate the possibility of any beta software (not limited to VS2010 or even any programming-related product) from causing you trouble. Choose any from this list, which is by no means exhaustive:
Don't use it on the same data (be it accounting information or source code) until you've run it in parallel and gotten the same results as with the older version.
Plan a backout strategy if the software is so bad that it's easier to go back than to try and go forward.
Backup your data even more frequently during the periods where you're using the beta software, up until the point that you're comfortable with it and can revert to a more normal backup strategy.
Don't use beta software at all - wait for the real release (or SP1 if you want to be even safer). There may not be a driving force behind updating to the latest version.
As a company, limit your exposure to the beta software to a small set of your employees. So, for example, if you have six different teams, choose the least important as a sacrificial lamb, so to speak.
My own personal preference is to wait until everyone else has sorted out the problems first. I didn't upgrade to the latest Ubuntu while it was in beta (I still got burnt a little bit with the video and X but that particular problem already had a solution on the net). I don't download the latest and greatest Eclipse until it's been in use for a few months. I'm still using VS2008 under Windows XP since there's nothing I think I need in the latest release (of VS or Windows).
We obviously have the latest and greatest OS' in our test environments but they're crash-and-burn environments that won't cause any real pain if they blow up (other than a rebuild but even that's pretty painless nowadays).
For your particular circumstance, I would probably stick with a tried and true version. You don't seem to have a pressing need for any of the new features in your question and the sort of failure you're talking about is not just losing some information at work which, while annoying, is probably backed up to the point where your career would survive.
A similar loss of your educational work would affect you for a long time if you fail your subject because of it. I would probably just concentrate on getting it finished rather than worrying about what VS2010 beta might do to my work. Don't misunderstand me, you should still be protecting your work even with VS2008 but I'd personally feel safer with that option.
Then, if you have some spare time at the end of your project (hah! as if that would happen!), you could try to convert what you've done so far to VS2010. If it all goes pear-shaped, you still have all the VS2008 stuff available.
There is certainly risk in using unproven software in that it could behave unexpectedly. Some of the answers here focus on protecting your source code and that is a valid concern, but you should also consider other risks.
Could Visual Studio 2010 make your system unstable? Having your source code in a local instance of source control won't do you much good if Visual Studio corrupts your hard drive. Even if you backed up regularly, you'd still be out a good day or two (MINIMUM) rebuilding your desktop.
Also, what do you intend to do with the finished product? Will a professor attempt to open the project on their own desktop? Are you expected to deploy it to another environment? We see these "Works on my computer" problems using proven software, a beta certainly increases the probability of running into this type of problem.
So yes, there is certainly increased risk in using a beta. You can take steps to mitigate the risks but with important work those are steps you should be taking anyway. Is the benefit of using Visual Studio 2010 worth the increased probability of delays / data loss / grade impact?
I know I'm experimenting with VS2010 and I haven't seen severe problems but betas are not proven/guaranteed - the overall risk is probably slight but it is a risk nonetheless.
I guess I would approach the question differently...Is there any real value in using VS 2010 over 2008? I have been using both for a while and I would say, No.
I have had some mysterious crashes with VS 2010 and the application has disappeared on me, causing me to lose any unsaved data.
If you are integrating IronPython / Ruby or working with Office or VB style COM, there is more support for this in .NET 4.0. Beyond that, most of the changes add some shine to the IDE, but not much real value.
my 2 cents.
The biggest risks you will face are crashes, random tool window misplacements, and occasionally Visual Studio will refuse to start and you will have to reset all your settings to have it working again. 1 (I am anyway reasonably happy with Visual Studio 2010 and don't regret having installed it; in my case the compelling reasons were unit testing and visual designer for Silverlight)
But as ocdecio says, there should not be danger for your code, especially if you use a source control system.
As an additional advise, target your projects to .NET Framework 3.5. Using a beta development tool may be ok, using a beta .NET Framework in a production environment is usually not.
1 This crash is supposed to be caused by using raster fonts for the code editor, but it has happened to me without using this type of fonts.
Given that you've said the project will be "tested on another system", the answer is simple: use VS2008. VS2010 solutions cannot be opened by earlier versions, and I wouldn't bet my graduation project on whether or not someone else has VS2010 installed.
Other reasons to stick with VS2008:
VS2010 probably doesn't gain you much.
There are bugs, and I'd rather be working on getting my graduation project done rather than working around problems with my development tool.
If you need help along the way, those that can potentially help probably aren't using the same version. That may make a difference, it may not.
Another thing to consider.. usually the EULA prohibits you from deploying and/or shipping a product using a Beta version of the toolset. I'm not sure this applies in your situation but it's a point to consider.
Another potential issue I've heard of is that sometimes Visual Studio betas refuse to uninstall when it comes time to put in the RTM version. So as long as you don't mind reinstalling Windows when you're ready to install RTM and you've taken the other answers into consideration, then go ahead.
Since your project is for a graduation project and not for full production release, I would say use the latest/stable version of Visual Studio 2010.
You will gain more than you will lose as you will be using the latest technology which will be more useful going forward.
There is an issue for touch screen machines which may render WPF applications unusable.
A workaround exists. See details:
‘MS.Win32.Penimc.UnsafeNativeMethods’ Threw An Exception
fix: C:\Windows\Microsoft.NET\Framework\v3.0\WPF>regsvr32 PenIMC.dll
The biggest problem I have with VS2010 Beta 2 is designer. The Windows Form Designer generates buggy code (Microsoft Connect bug id 507267 and 499925). So I have to edit the form in older version of Visual Studio
I have a few other problems not related to code lose, like random crashing and wizard disappearing.
I've just spent two weeks in VS 2010 beta 2 doing some serious prototyping work. It all went pretty smoothly, and I really like VS 2010. At the end, I moved all the code back to VS 2005 and integrated it with my current project. My experience:
Moving the code back to 2005 was pretty easy. I did try not to use any C# features from 2008 or 2010. The only thing I missed was C#'s implicit properties, but those are easily fixed.
Yes, the project and solution files are not backward compatible. To migrate back, I just created new projects in 2005, and pasted the source files in through Visual Studio. Worked like a charm.
I did find one thing that would consistently crash 2010. If you use the splitter to view two different sections of a file at once, and cut-and-paste from one pane to the other, VS 2010 will roll over and die pretty quickly (not necessarily at the time of the cut-and-paste, but very soon afterwards).
There are some nice productivity features in 2010. You can drag a tab out and make it a window. In Windows 7, you can drag it to the top of the screen to maximize, or to the side to use have the screen. Dragging one file to one side of the screen, and another file to the other side, means you get the whole screen to edit two files, side by side. Very nice. (Even better on two monitors, but I was on a laptop.) The "Quick Find" dialog can now be docked -- that's a huge improvement.
As others have mentioned, use source control, but VS 2010 really is not unstable enough to be any more of an issue than VS 2008. Note that Team Foundation Server 2010 is also available in beta, and will be part of all MSDN subscriptions. It installs under Win7 and Vista. I'm using it for source control on my laptop! Team Explorer is integrated into VS 2010.
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.
Not sure if anyone has noticed this yet but if you run Visual Studio 2008 with the DBML (not sure about EF yet) under Windows 7 the tables will disappear when you hover over them. Looking for a fix so I thought I'd ask everyone since I've seen it asked in comments but not as a question yet.
EDIT
I've filed a bug with Microsoft. Anyone else who wants to help get it fixed please validate it as a bug.
It's unlikely that there is a published fix available for this. Windows7 is still a non-RTM product and will have bugs with existing applications. Since the issue is more likely to be in Windows than Visual Studio, the fix will almost certainly come from Windows.
Your best bet is to upgrade to the next version of Windows7 when it comes out and hope it permanently fixes the issue.
A short term solution is to disable Aero and see if that helps. I've found that occasionally fixes graphics issues for me.
EDIT
I was able to confirm this exists even on newer builds of Win7. It's almost certainly a bug in Windows vs. Visual Studio. But this bug will get actioned much faster if you file a bug on Visual Studio. I've included the bug link below. I'm going to follow up internally but this is likely to get attention faster if it's filed by a customer.
http://connect.microsoft.com/VisualStudio
There's a related bug which pertains to the Entity Framework EDMX Entity Model Designer on Windows 7 RC. So the DBML designer is still broken.