I've got Visual Studio 2010 Ultimate edition on my machine, and I've been working with ASP.NET a lot (my job). I recently installed Visual Studio 2012, to test it out. Noticed that I had a few issues with VS 2010 after installing VS 2012, with Unit Testing etc.
Anyway, I have been debugging & testing the ASP.NET pages in 2012 to test it out. Went back to debug and test on VS 2010 and that's when it all went wrong! Sometimes it debugs, most of the time it doesn't, and when it does the layout and formatting is horribly wrong.
Tried the ASP.NET project on my employee's machines, and it runs fine and the layout is all correct. (They use VS 2010)
I've uninstalled VS 2012 completely and tried debugging and testing in VS 2010 and I still have the same issue! I also have re-installed VS 2010 twice, and yet it still does not work.
Anybody know whats wrong with it? Or what else I can do to ensure VS 2010 and 2012 stuff has been properly uninstalled before I try another re-install?
Thanks for your time..
Create a Virtual Machine and install VS2010. In a clean install, it should work fine. Otherwise, VS2012 could have made some changes to your code. I wouldn't discard it -¿config files? ¿a new version of the bundled web server? ¿a new functionality?-.
Once you have discarded code changes due to the new version, give a try to your preferred uninstall software and delete VS2012...
Related
I am trying to convert my current asp net application to an ASP.Net vnext application and I am trying to figure out if we have have to use Visual Studio 15 or visual studio 14 ctp 3 for vnext to work? Will it work in visual studio 12 or 13?
I found this link
http://blogs.msdn.com/b/dotnet/archive/2014/08/18/try-out-the-new-releases-net-framework-vnext-asp-net-vnext-net-native-and-ryujit.aspx
and I haven't heard any updates.
If you want to use Visual Studio, you need Visual Studio 2015 and CTP6.
Good news is, you can have VS2015 installed side by side with 2012 or 2013 with no problems. (really!) And if you are not yet familiarized with the command line tools, I do highly recommend to install vs2015.
For migrations, there's some documentation in the workings on the Docs repo.
check this out : https://github.com/aspnet/Docs/blob/master/docs/migrating/migratingfrommvc5/migratingfrommvc5.rst
this is just one, there are a few more doc pages on that repo that might help you to get started and see which changes should be made and how to apply one by one.
Unfortunately the documentation is not finished and there's not much about it, so be prepared to have patience because you will be migrating and learning a new stack in the process.
Microsoft team has been very active and helpful in all channels (twitter, SO, github, etc) so, you can at least get help if you find a block.
The tooling for ASP.NET 5 is only available for VS 2015.
However, you can build and run ASP.NET 5 applications outside of VS using the command line tool and other editors.
I am using the latest version, 1.0.82.0 (sqlite-netFx40-setup-bundle-x86-2010-1.0.82.0.exe), and am using the released version of Visual Studio 2012 with all the latest everything.
I do not see the SQLite in the Designer Data Source in Source Explorer (new Connections).
The download on SQLite states, "This setup package is capable of installing the design-time components for Visual Studio 2010". I presume the "Visual Studio 2010" part is why I do not see the designer in VS2012, which is what I have.
How can I get the designer to work with VS2012?
When will the System.Data.SQLite.org team come out with a version that works with VS 2012?
(I did see a couple of posts back in July which talked about 1.0.66 and 1.0.73, but that was then and 1.0.82 includes the designers just for VS 2010 apparently. I see other file names with "-2008" presumably for Visual Studio 2008. That means that a Visual Studio 2012 will probably come, but in the mean time, I am curious about a manual registry hack or something like that.)
In order to get designer support for SQLite in Visual Studio, you have to download a very specific version of System.Data.SQLite. The downloads page has an astonishing 56 different possibilities, so it's easy to get the wrong one.
Look for the big bold text that says this:
This setup package is capable of installing the design-time components for Visual Studio 2012.
But it's still easy to miss among the zillions of downloads. If you need to, use Control-F to find the "Visual Studio 2012" text.
Don't download the 64-bit version, even if you're on a 64-bit machine. You need the 32-bit version with the text above to get designer support.
NEW EDIT NOW I GOT IT WORKING!
Goto Visual Studio, Manage Nuget, search for online packages, search "SQLite", install System.Data.SQLite, and boom, you can use designer and evrything is working again.
After some search I found my answer, 1.0.83, which will come out in November XX, 2012.
Visual Studio 2012 aside from the v10 to v11 registry hive difference also has what the team calls a "redesigned designer support".
Here is the link to the information.
http://system.data.sqlite.org/index.html/doc/trunk/www/news.wiki
1.0.83.0 - November XX, 2012 (release scheduled)
•Updated to SQLite 3.7.15.
•Add Visual Studio 2012 support to all the applicable solution/project files, their associated supporting files, and the test suite.
•Add Visual Studio 2012 support to the redesigned designer support installer.
and other changes.
I could not find any interim solution on the web, sadly. The lack of a fix affects report based projects with DevExpress and projects that use the explorer.
We've got an older ASP.NET app written in VS 2005. I'd like to upgrade it to VS 2008, but still leave the old one around, in case I need to do development in it. It is also in Visual SourceSafe. So, would I just get into VS 2008, do an Open Website from Source Control (or whatever the string is) and put it into a new website under wwwroot?
open the application in VS 2008. VS will automatically detect the app is VS 2005 and offer to upgrade, with a backup. Do that. Usually there aren't issues with an upgrade.
Not exactly a programming question in the technical sense, but it's impacting my development nonetheless and I'm hoping someone here might have encountered and solved this issue before.
I recently got adventurous and installed Office 2010 beta onto my PC here, and I've noticed that Visual Studio has begun to hang whenever I'm editing an ASPX file, sometimes right away, sometimes after a few minutes. In my research I came across this post:
http://abdullin.com/journal/2009/5/12/visual-studio-2008-locks-or-freezes-in-aspx.html
It seems to imply that there's a dependency between Office and Visual Studio. Is anyone here successfully running Office 2010 64-bit with Visual Studio 2008? I'm on Windows 7 64-bit, also.
Josh
Edit: I have confirmed that the Setup.exe file referenced in that post is in fact being run by VS. It is indeed a vestige of the Office 2007 suite. I moved the directory it was in, and (of course) the process isn't spawned, but VS hangs on "loading cache" on this project. I think I'm getting closer though.
Hope this helps:
http://blog.hinshelwood.com/archive/2009/07/19/office-2010-gotcha-2-visual-studio-2008-locks.aspx
Unfortunately, doing a repair install of the Office-based Visual Web Developer component wouldn't work — the setup application kept crashing. I ended up solving this problem by doing a complete reinstall of Visual Studio. For some reason, doing a simple repair wasn't possible — the VS setup kept crashing, too.
I did a manual remove using an uninstall tool designed for the VS2008 RC. It did a complete install of all VS components, after which point I reinstalled VS2008, which in turn reinstalled the Office-based visual web developer component.
It was a long and painful process, but it worked. It didn't seem to be a direct incompatibility between Office 2010 and VS2008, as we have another PC here with the same combination that wasn't having the problems. I believe it had to do with the fact that my PC originally had Office 2007, which I had to uninstall before installing Office 2010. The other PC that wasn't having this problem never had Office 2007. I can only assume that the uninstall process for Office 2007 either removed those Visual Web Developer components or removed dependencies that were originally put in there by the VS2008 setup program.
office 2010 runs on wpf and its major portion is build on dotnet framework. And there is always connectivity between office and vs coz vs can make office apps also. If you use office 2010 as your default for aspx page editor and vs is also opened with the same project. it will sometimes hang due to lack of resources and also vs 2008 was made for 32bit os, so if ur running it on 64bit os with office 2010 64bit it can sometimes cause problem of resouce management. Already wpf uses hell lot of resouces and then 32bit vs 2008' connection to it will use more resouces.
So what i suggest is try to use 32bit 7, 32bit office 2010 ans vs 2008.
Regards,
Apurva
I have Visual Studio 2008 SP1 and ASP.NET MVC RC installed on a XP SP2 machine with .NET Framework 3.5 SP1. (That's a lot of SP's in one sentence!)
I've a ASP.NET MVC project that I can edit just fine with Visual Web Developer Express.
But opening a View page in Visual Studio 2008 SP1 makes Visual Studio to crash and vanish without even giving an error message.
Now, some bloggers have proposed that either Visual Studio Power Tools of TFS Power Tools could be causing this. However, I have neither installed.
Visual Studio can be started with /SafeMode option which solves the issue. But I'd like to know if there's more elegant solution available?
Pom
Microsoft have now released a hotfix to resolve this issue.
See https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=16827&wa=wsignin1.0
Phil Haack elaborates here - http://haacked.com/archive/2009/03/06/hotfix-for-installing-aspnetmvc.aspx
What solved it for me was clearing the Native Image Cache.
go to %windir%\assembly and delete the folders that start with NativeImages. I Have two... NativeImages_v2.0.50727_32 and NativeImages_v2.0.50727_64 because I'm running 64-bit Vista.
I had this same problem a few days back, and I removed all examples of Microsoft.VisualStudio.QualityTools.UnitTesting.Silverlight.dll. I found the solution on google, and like you I'm not running PowerTools. I guess you're seeing
.NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (7A035E00) (80131506)?
I renamed all examples of that DLL and rebooted, and now I can work again, don't know what I'll do when I have to unit test SilverLight again though.
Answering to myself here:
I eventually removed Visual Studio add-in called Ora. That seemed to stop MVC View related Visual Studio crashes.