I cant seem to find any useful information whether constructor delegates that are proposed for C++0x are already available in Visual Studio 2008 / 2010. I tried to use them and got pretty strange errors, but I can't test this in VS2010 currently. Can anyone tell me if they are available already?
cheers,
Tom
They aren't available yet.
:(
Related
I need some information about the differences of MFC between VS2008 and VS2010. For example I found some differences in OpenDocumentFile method (docmgr.cpp). Someone knows where can I find this information?
From the MSDN page - Breaking Changes in Visual C++ for VS2010:
I'm about to start a project where I will be likely to use a lot of C++/CLI. I really miss C++/CLI Intellisense in VS 2010. I've heard of some Resharper-like products for C++, but wonder if they provide complete Intellisense. Do they also work with C++/CLI?
What are people doing to overcome this limitation?
Visual Assist X, a commercial addin for Visual Studio developed by Whole Tomato Software
Yes, Visual Assist X does support C++/CLI because we make heavy use of it. Its a good product, give it a try. What it doesn't do, however is make browsing or F1 help work.
Visual Assist is rumored to have IntelliSense support. They don't advertise it, which is mighty strange. Better try to eval version to check.
Other than that, I don't doubt that most devs replace the missing support in VS2010 with VS2008.
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...
Someone could tell me where I can find the list (or all) patch already available for Visual Studio 2010.I am finding a lot of problems, and his navigation is very slow. Especially with ASP.NET MVC.
If no such list ready, we can use this post to enumerate the problems and their fixes.
Thanks
This page should have all the hot fixes
http://connect.microsoft.com/VisualStudio/Downloads
and check out the http://visualstudiogallery.msdn.microsoft.com/en-us/
its no "fix" but for example, there are replacements for the "add reference" dialog, that are muuuuch faster....
Here's a patch that correct a lot of problems that I've been finding in IntelliSense... It works perfectly for me:
http://weblogs.asp.net/scottgu/archive/2010/02/15/patch-for-vs-2010-rc-intellisense-crash-issue-now-available.aspx
Regards!
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.