I have developed a a MVC 3 application in Visual Studio 2012 express and I'm trying to create a web deployment package following the documentation in this link:
http://msdn.microsoft.com/query/dev11.query?appId=Dev11IDEF1&l=EN-US&k=k(WebApplicationProjects.PackagePublishOverview);k(TargetFrameworkMoniker-.NETFramework,Version%3Dv4.0)&rd=true
I have a couple of issues.
1. I cannot select deploy check box in the configuration manager, it is greyed out
2. The zip file is not being created
Is this a limitation of the version of visual studio or am I going about deploying this type of project wrong. Due to the nature of the application the web deployment package is the best deployment option.
Related
Just installed Visual Studio 2017 – Enterprise Edition with the following workloads:
Universal Windows Platform Development
ASP.Net and Web Development
.Net Desktop Development
.Net Core cross-platform Development
After this installation, when I create a new .net core or .net standard project, the visual studio restarts while loading the project template.
Steps to create the behavior:
File ⇒ New Project ⇒ .Net Core ⇒ Asp.Net Core Application (.Net Core)
Visual Studio tries to load the selected template then suddenly it disappears and the windows show the dialogue box to Check online help, debug or close it.
Next, visual studio reboots to the start page.
This only happens when I select any .Net Core or .Net Standard project templates.
Much appreciate your help in advance.
I had the exact same issue. It turned out that when a .Net core or .Net standard project template is selected, it tries to restore the packages from NuGet and somehow it was unable to do that or clear the NuGet’s local cache.
Here are the steps to fix it:
Download NuGet
https://dist.nuget.org/win-x86-commandline/latest/nuget.exe
Open the command prompt as “Administrator” – this is important other
cache may not get cleared due to permission issues.
Navigate to the folder where the NuGet is downloaded
Run the following command to clear the cache
nuget locals all -clear
Open Visual Studio 2017
Create a new ASP.Net core project with default templates
Hope this helps!
I recently downloaded Visual Studio 2015. When I wanted to create new project I chose file---new---project and I need to select asp.net mvc4 web application, but I couldn't find it I have only asp.net empty web application
and when I select it i have this error
Try to install Microsoft Web Developer Tools.
here: https://visualstudiogallery.msdn.microsoft.com/c94a02e9-f2e9-4bad-a952-a63a967e3935
It will enable MVC templates (and others web tools) for VS.
(maybe also the error goes away)
Send results. Att,
I am now using the Visual Studio 2013, where I want to create a web deployment installer for project like I am doing in Visual Studio 2008.
But I am not getting any option inside Setup and Deployment. Can anybody please guide me how to create the installer package for web application? I have publish folder ready with me. Can I create any installer from VS2008 using this Publish folder?
Visual Studio no longer includes a setup installer out of the box. This was removed in VS2012; the guidance instead is to use a 3rd party option like WiX or InstallShield.
Another option, if you don't need to use an MSI based installer, is to use Web Deploy. A web project in VS can create a deployment package, which can then be published to any number of websites at any time. It can also be customized by configuring parameters and setting their values at deploy time (link). Web Deploy packages can support deploying your web content, IIS settings, and database.
VS2013 will support it again. It will be released in the next update patch of the VS2013.
http://visualstudiomagazine.com/articles/2014/04/18/microsoft-reinstalls-visual-studio-installer.aspx
What is the difference between Web Deployment Projects (.wdproj) and new
MSDeploy?
Is it prefer to use MSDeploy instead of Web Deployment Projects?
Is this add-in created only for backward compatibility with already created Visual Studio 2005/2008 projects, or it's a product, which will be evolving?
Web Deployment Projects and Web Deploy (aka MSDeploy) are not mutually exclusive; you can use a WDP to create a Web Deploy deployment package. Web Deploy is an IIS tool that can be used by Visual Studio or MSBuild. In Visual Studio 2010 the Web Publishing Pipeline is implemented using MSBuild so that it can work the same way from the IDE (the one-click publish feature) or by invoking MSBuild targets from the command line. See this MSDN page:
http://msdn.microsoft.com/en-us/library/dd394698.aspx
If you're using VS 2010 or later and you are using web application projects rather than web site projects, you don't need Web Deployment Projects unless you want to build a precompile/merge step into deployment. If you're using web site projects, you still need to use Web Deployment Projects.
WDP's days are numbered, it will not be evolving.
We are using Visual Studio 2010 to publish to IIS using Web Deploy. I have now upgraded to Web Deploy 2.0 on the client, and the server (by uninstalling the old version and installing the new version).
From Visual Studio, it still seams to be creating web deploy 1.0 packages. This is where I am confused. How does Visual Studio integrate with Web Deploy? How do I get Visual Studio to create Web Deploy 2.0 packages?
Thanks for your post.
I just found a doc might help, it illustrates the installation and enabling of web deploy:
http://weblogs.asp.net/scottgu/archive/2010/09/13/automating-deployment-with-microsoft-web-deploy.aspx
Moreover, I think web deploy is more relevant to ASP.Net, and if you can post another thread at:
http://forums.asp.net/26.aspx?Configuration+and+Deployment
I believe you can get more useful information.
Hope this can help.
I got it working. The batch file that was being generated by web deploy was checking for v1.1 in the registry. Editing it to check for v2 works on a server that only has v2 installed.
After installing the Visual Studio service pack, I see now that the batch file is different, and no longer does a registry check so works with web deploy clients 1 and 2.