I have Visual Studio 10. I installed SP1 and I can not create an MVC web project. Is there anything else I need to install?
As mentioned, you will need to do use File -> New -> Project and under Web you should be able to see the MVC project templates.
Reference: I encountered the same when I was just starting with MVC.
From your comments it looks as if you have the solution you're seeking, however I would like to mention for the sake of others that if you want to develop an MVC3 application on VS2010 SP1, you will still need to install it.
More details here.
I'm not aware of any good reason to not use MVC3 for new development, as it's contains many improvments over MVC2.
Related
When i want to use Visual Studio to open new Telerik MVC project, everything is OK but, it is not Bootstrap3. It shows, old design of ASP.net projects.
Should i need to configure anything ?
Regards.
You don't have the latest Visual Studio template.
Check here: http://docs.telerik.com/kendo-ui/aspnet-mvc/vs-integration/introduction
if possible I need total from the beginning utter beginner advice on how to get my ASP.Net MVC 3 Razor Visual Studio 10 web application live onto my IIS 7 webserver please?
I've never tried to publish this before, and wondering what I'm missing?
I've clicked "Publish" on Visual Studio Express 10, created a "published" version of the website. I've uploaded it to my webserver, however can't make it load on the net?
Appreciate some guidance please? (not sure how / what default documents work etc...?)
By far the easiest approach is to use Web Application Deployment.
This blog by Scott Gu gives a great intro
http://weblogs.asp.net/scottgu/archive/2010/07/29/vs-2010-web-deployment.aspx
The article talks about web.config transformations (ability to have a .Release and a .Debug version of your web.config). Later, that capability was generalized through an add-on package to work for any XML-structured file in your deployment (for example, I use it with NLog configuration files).
http://www.hanselman.com/blog/SlowCheetahWebconfigTransformationSyntaxNowGeneralizedForAnyXMLConfigurationFile.aspx
I maintain a couple of legacy ASP.Net webforms solutions, that I have upgraded to use .Net 4.
However, they appear to be different in Visual Studio 2010, than other projects. If I open properties for one of the web projects in the solution, it looks like this:
The old-school dialog from previous versions. No fancy publishing and other neat "new" stuff.
What is going on here, and how do I fix it?
You appear to have created a New Web Site...
You're looking for Web Application it sounds like. Go to File > New > Project..., and ASP.NET Web Application is under there. You may also want ASP.NET Empty Web Application as it doesn't have some auto-generated junk in it.
We are facing a very weird situation using Visual Studio 2005:
There is a Web Site project we do have, and VS when compiling the project automagically adds some undesired references, like 'System.Data.Oracle' (we don't use Oracle at all, and never did) and things from asp.net 3.5 (the project is 2.0, we don't use in it anything related to the new version).
As a consequence of this, when putting the published site into the production server (configured for 2.0, without these strange dlls), the site doesn't work. Even if we remove these dependencies from Web.config file.
Have any of you ever seen something like this happening with your VS05?
Note: the bin folder doesn't have these dlls.
Save your sanity and stop using Web Site Projects. They were an abomination from the get go.
The conversion to Web Application projects is well worth the effort.
Are you using Visual Studio 2005 SP1? You should be. There are bug fixes in addition to the fact they added Web Application Projects back.
VS2005 isn't inventing these references. Something in your web site is using them.
Are you precompiling the site prior to deploying it?
We could resolve it!
The web site project references a project.
This project had all these references, and the web site used them.. Removing the undesired references resulted successful ;)
In the very near future I'll be migrating some web applications from VS2003 projects to VS2005 projects.
What should I watch out for?
Anyone done this in the past and have it go bad?
How much time should I expect it will take to migrate a project?
I know this is more than one question, but please provide your experiences with anything relating to migrating projects from VS2003 to VS2005.
Thank-you
EDIT
The types of projects I will be migrating are Web Applications written in Visual Basic.
Do you absolutely have to go to VS2005 rather than straight to VS2008?
Even though Web Application Projects were implemented for VS2005, first with an add-on, and later with a service pack, IIRC, upgrading VS2003 web projects was extremely flaky.
We had a dozen or so production web sites (all written in VB.NET) running ASP.NET 1.1, and wanted to move forward... it proved a complete nightmare (even with Web Application Projects installed), and we gave up since we didn't have the resource available to persevere.
Then VS2008 came along, and I had another go.
Bingo, no problem at all. The project upgrade wizard just ran, there were a few trivial code fixes, and it just worked.
Straight from VS2003 to VS2008 in about an hour. All the sites ran off the same code base, and upgrading was as simple as copying over the folder, and changing the IIS management tool so that it specified ASP.NET 2.0.
I imagine you can guess what my recommendation would be!!
Be aware of the differences between a Web Site Project and a Web Application Project.
I really would go straight to VS2008. You can 'throttle back' your project so that it 'only' uses .NET 2.0, if that's a requirement.
As far as what to watch out for - ASP.NET 1.1 and ASP.NET 2.0 are very different creatures, I've discovered. ASP.NET 1.1 let you put objects on a web page much the way you would drop buttons, labels and text boxes on a desktop forms application. This is no longer true in 2.0. I had a LOT of self-education coming to me when I started working on my current project in that I really had to learn how to lay out presentation-layer stuff with ASP tags (divs, style sheets, etc). The code-behind was still the same - handled better in fact. This all depends on what kind of web projects you're migrating and how they were written in the first place.