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.
Related
I changed my Windows and when I installed Visual Studio 2017 again and opened my project, I realized I needed to install the ASP.NET Core 2.2 software development kit so that Visual Studio 2017 could read my ASP.NET Core code.
I installed the software development kit, but nothing changed at all - can anyone please help me?
I have installed all the software development kits of ASP.NET Core 2.2 and they can be seen on my C: drive.
this is what I get
Open visual studio installer and goto ASP.NET Web Development and check SDK core 2.2 for automatically install ASP .NET Core 2.2.
If you need to install manually than Click for ASP .NET Core Runtime and Click for ASP .NET Core SDK.
Go to this page https://dotnet.microsoft.com/download/dotnet-core/2.2 and download the version 2.2.7. It works with Visual Studio 2017. For some reason you need to click through the readmes and end up here https://github.com/dotnet/core/blob/master/release-notes/2.2/2.2.7/2.2.7-download.md. Then half-way down the page there is a link to the 64 bit (probably what you want) and 32 bit (probably not what you want ) Windows SDK installer. This seems a bit involved but they are all Microsoft sites. Remember to restart Visual Studio after installing.
In general, you can always find what you need to download by going to dot.net (clever, no?) and following the thread of information there.
Good luck.
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 have one web application in C# which is developed using Visual Studio 2010 and I want to convert or Migrate that web application in Visual Studio 2013 (C#).
Note:- Below listed things I used in my current Web Application using VS2010 (C#)
Asp.Net Server Controls.
ClassLibrary (.dll).
Web services.
Above Listed things I used in my current Web application which is in VS2010.
Now, My Question Is- What would be the major changes I would be facing if I am using all above listed Microsoft Technologies using C# and Migrate it to VS2013.
The biggest change for us was that Visual Studio Setup Project was depreciated in VS 2012, so we had to build new installers.
http://blogs.msdn.com/b/visualstudio/archive/2013/08/15/what-s-new-in-visual-studio-2013-and-installshield-limited-edition.aspx
Also, which version of .NET is you application? Keep in mind framework targeting for Visual Studios (basically if your application is .NET 3.5 SP 1 or newer you should be fine):
https://msdn.microsoft.com/en-us/vstudio/dn250998.aspx
The Web Services should also be okay, if you intend to keep creating web services instead of switching to WCF, you may want to look at this:
Create a asmx web service in C# using visual studio 2013
The thing we first noticed is VS2013 uses IIS Express 8.0, at the time our production web server was IIS 6 - we encountered, on numerous occasions a web.config setting working fine locally but forgot to add the IIS 6 equivalent.
For our web apps we kept targeting the same .Net framework and I can't recall any issues. For your reference our stack was Asp.Net MVC 4, EF 5 WebApi plus numerous NuGet packages. So we didn't have any asp.net server controls.
You may also want to ensure all your VS2010 plugins have a 2013 equivalent.
You shouldn't have any problem at all with the types of proyects you are using.
You could even open the solution with VS2013 and then open it back with VS2010 SP1 without any problem (as long as you don't switch the .NET framework to 4.5).
Starting from VS2012, Microsoft made changes to allow developers open a solution with older versions of VS (VS2010 SP1 being the oldest version that supports this). There ARE some proyect types that won't be compatible, but from the things you listed, you won't have any problems.
When you open the Solution with newest VS, it WILL make some changes, but you still will be able to open it with VS2010 SP1 (again, with some exceptions).
https://msdn.microsoft.com/en-us/library/hh266747.aspx
http://blogs.msdn.com/b/webdev/archive/2012/08/22/visual-studio-project-compatability-and-visualstudioversion.aspx
Anyway, my suggestion is, install VS2013 in a test machine and try it out. You can even create an Azure VM with VS2013 PreInstalled in minutes to try it out.
There is already available VS2015 preview, why not wait until it is released? (or use the preview)
https://www.visualstudio.com/en-us/downloads/visual-studio-2015-downloads-vs.aspx
as other said, it should not brake much
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
Ok so i downloaded the asp.net mvc through the web platform installer. Rebooted the machine and fired up VS 2008 express. Lo and behold there were no website/project templates that could setup an mvc project. I did a little research and found out they would not show up in the express version. No matter - i got team suite edition too so i installed that and hoped for the templates to show up. They did not, so i reinstalled the mvc and they still won't show up.
I hate this part of developing - i just want to dognammed tools to work - what am i doing wrong - why won't the templates show up? I can't seem to uninstall mvc now and reinstalling just tells me that it's already installed...
If you have asp.net mvc installed and don't see templates in visual studio, you should try to run administrative command prompt and run devenv - setup so that templates can be registered.
c:\Windows\system32>cd "C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE"
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE>devenv - setup
this should help
If you installed Team Suite after mvc, it won't see the templates. Try reinstalling MVC, it's light and shouldn't take long.
Are you sure? I thought that but it HAS to be .NET 3.5 AND it's a Web Application from the New Project dialog and not through the New Website dialog. Annoying but alas!