I was used to building on .Net Compact Framework 1.0 with VS 2003 where you had the option to "build CABs" for your project, which is handy because I am sending the app to a remote site.
Now this project was rebuilt with VS 2005 and I don't have this same "build CABs" option. Is the deployment model with VS 2005 just to send the contents of the bin\Release folder?
For VS 2005 I would add a Smart Device CAB project to the solution and create the CAB with that using the primary output of the original project.
The Smart Device CAB project can be found under Other Project Types/Setup and Deployment
Related
I've previously created an ASP.NET Core project with .NET Core 2.0 preview 1 and Visual Studio 2017 15.3 preview. Just the default stuff from the project template, no custom code yet. Then I used the Publish command and have everything copied to the directory bin\Release\PublishOutput. All nice and good. 5 MB, can be deployed to the production web server and it works.
Now I've tried the same thing with VS Code and just won't get anywhere. I created the project with dotnet new mvc and opened it in VS Code with code .. After closing and opening it a few times and editing .cs files, I think I've now jumped over all the hurdles that VS Code comes with. I can run the application locally.
But the publishing doesn't quite produce the desired result. I run dotnet publish -c Release manually because VS Code doesn't seem to offer anything here. I get tons of files in bin\Release\netcoreapp2.0, along with a subdirectory called publish. Both have a copy of MySite.dll and MySite.pdb, but no precompiled views DLL. Also, the publish directory has 54 MB of runtime DLLs that weren't required for what Visual Studio gave me.
What is the intended method to publish an ASP.NET Core MVC application with VS Code? Everything is the latest version, downloaded and installed today.
Do I need components from the full Visual Studio to get the complete publishing experience, with all the advertised features?
For the record, I have recently discovered in ASP.NET Core 2.0 preview 2 that this has been resolved. A project created with dotnet new mvc has the MvcRazorCompileOnPublish property set in the csproj file, and dotnet publish does the same as publishing through Visual Studio 2017 (15.3) now.
I am creating a Web Setup Project using Visual Studio 2013 to create a MSI installer for an ASP.NET Web API project. I am using this extension from Microsoft that brings these projects into VS2013.
I am trying to understand what the Web Setup Project does in relation to IIS. It appears there is no difference between a Web Setup Project and the standard Windows Setup Project in what it actually does. They both install the files to a directory that I choose during installation. I would expect the Web Setup Project to create a site/virtual directory in IIS but it's not. It doesn't do anything different than if I use a windows Setup Project.
Is there something else I need to do to make the Web Setup Project install a site/virtual directory to IIS? Or is the correct behavior to just install the files to a directory and that's it?
There is no documentation for the VS2013 version of this but I am looking at the reference here for VS2010 and the product appears about the same
I have a TFS project that has multiple .NET 3.5 projects.
I want to create a windows phone 8 project in the same solution cause it will reference a a .NET 3.5 library project and a WCF project.
when my colleagues get the latest version from the TFS, they can't load the solution cause they don't have Visual Studio 2012 (which is used for the windows phone project).
is there a way to add my windows phone project to the TFS solution without affecting the other older framework projects ?
I suggest you to add your project normally (Add Existing project to source control), but when you chenck in, you don't check in your solution file. with this solution you save your code in repository without affecting basic behavior
I've been working on an ASP.NET MVC 2 (.NET 4.0, Visual Studio 2010) application for a while and have decided that I would like to deploy it as an Azure application.
After installing the latest (June 2010) Azure tools (through Visual Studio itself) I've added a blank CloudService to my solution. Whenever I try to add a "Web Role Project in Solution", however, I get the following error:
An error occurred trying to load the project properties window.
Close the window and try again.
Cannot evaluate the item metadata "%(FullPath)".
The item metadata "%(FullPath)" cannot be applied to the path
"obj\Debug|Any CPU\Cloud.dll". Illegal characters in path.
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets
I get this same error whenever I try to Save All or view the properties page for the CloudService project.
I imagine it's having trouble with the Debug|Any CPU part of the path, but can I remove it or word around it?
Thanks in advance
Well, what do you know. When had already sort of given up on this, seeing as how I could run en deploy the application anyway I decided to try one last time and ended up finding the solution on this article:
http://tomkrueger.wordpress.com/2010/07/27/azure-deployment-issue-after-upgrading-to-visual-studio-2010-and-net-4-0/
The problem started because I actually added an Azure project to an existing ASP.NET MVC solution there were some unnecessary settings left over in the web.csproj file.
All I had to do was open web.csproj in notepad and remove all occurrences of the <PlatformTarget> element.
My MVC prjoject was x86 and of course Azure works on x64 only. Even though I had the platform target set up as AnyCPU somehow Azure couldn't quite get along with it.
Have you downloaded the latest Azure SDK? .NET 4 was not supported before the June 2010 version of the SDK.
Windows Azure Software Development Kit (June 2010)
Windows Azure Tools for Microsoft Visual Studio 1.2 (June 2010)
How do I publish a C++/CLI Windows Forms project for ClickOnce deployment? The properties window for C++/CLI projects does not include a "Publish" tab (like in the C# projects).
You can follow the guidelines for manually deploying a ClickOnce application on MSDN.
This relies on the Windows Software Development Kit and command line tools instead of Visual Studio to do your deployment.
Just another note with this - if you can, I'd recommend trying to migrate to /clr:pure if possible. If you're working with native code, this won't work, but if it's a pure windows forms app, it will make the deployment scenario simpler, since you'll have fewer issues in ClickOnce with CAS requirements.
You cannot ClickOnce deploy an exe written in unmanaged code. The standard approach is to create a managed code stub exe that would launch your actual application.
Here's a related question.