I'm creating an asp.net application/plug-in to run on a asp.net website/e-commerce solution. I want to make deployment easy for the user so that all they have to do is double click on an icon and all of my apps files will be placed into the proper folders on their asp.net website and all the necessary third-party files, like Microsoft's Visual Fox Pro 9 dll, will be installed. Is there a good tutorial or reference I can view to learn how to handle these deployment issues and are they even possible?
thanks
You can make an MSI (Microsoft Installer) which will do most of the work for them.
From Programming Microsoft ASP.NET 3.5 by Dino Esposito
Precompilation for deployment creates
a file representation of the site made
of assemblies and static files. This
representation can be generated on any
machine, and it can be packaged to MSI
and deployed.
Create an MSI is definitely a good
option to do this.
If you already have all the output
with dependencies, then a batch copy
script can do that for you.
If you are building from your
source, then take a look at
MsBuild/NAnt,and you can moidfy some
post-build script to do that batch
process for you.
You can also take a look at web
deployment project.
Related
Is this possible?
We currently have build definitions and release definitions setup and working for Web Applications. However we have a lot of older web site type projects and will not work with the current build and release definitions that we already have setup.
Is there a way for us to get the web site projects to work with the build and release definitions in TFS?
Thanks
Recently changed my steps for the build definition and now that build is successful but the release still fails.
Build definition Steps are:
Nuget Installer, Copy Files, and Copy and Publish Build Artifacts
Release definition Steps are:
Powershell on Target Machines, and Windows Machine Files Copy
As web site projects needs bin folder and TFS doesn't want them to be stored in source, the best way to achieve is to convert web site projects to web application.
Best practice: Converting to web application:
https://msdn.microsoft.com/en-us/library/aa983476.aspx
But they made a workaround maybe you can try:
https://blogs.msdn.microsoft.com/tfssetup/2016/09/21/building-a-website-with-tfs-build/
In previous versions of what is now .NET Core, using the dnx toolchain, it was possible to run an application straight from source code, without compiling to a DLL on disk. This capability was also present on Azure, allowing you to edit code on the server and have those changes reflected in the live site.
The new dotnet CLI run command seems to automatically create the familiar bin and obj folders with compiled DLLs in them, and the publish process from Visual Studio to Azure now no longer includes the C# source, just the DLL.
Is it no longer possible with the new CLI and other tools to run .NET Core code without creating a DLL on disk?
Short David Fowler response:
Dynamic compilation is gone in RC2. It only exists for views now. There are no plans to bring it back.
Why?
Architectural challenges and changes require to implement it on both .NET Framework and .NET Core. We did it with dnx and there were some problems (like some things being completely broken with in memory assemblies) that we chose to just avoid.
I have an asp mvc project. I'm wondering, what's the difference between building the solution and then copying bin and all other views/scripts/images/style sheets and publishing (besides the obvious work of copying files). I'm asking because i want to automate my deployment with rake and I can't use web deployment because it's not compatible with mono.
Depending on your version of Visual Studio and settings, Publishing typically does two main things in addition to the build
Packages the solution
-- usually into some standard format (WebDeploy, Web Project)
Automates deployment
-- typically hooks something like MSdeploy ("web deploy") to synchronize the site with a local or remote IIS setting
So in terms of what you are deploying, there is no difference. The build and output files are the same. Publishing is simply allowing a developer a simple path of packaging + deploy, which you are handling with rake.
BTW Have you looked Uppercut this tool could be very useful in your build process.
What's the recommended way to deploy a website created with ASP.NET 4.0 and Visual Studio 2010?
I've previously always added a web setup project to my solution, and used that to create an MSI, even for small applications.
But when I build a web setup project in VS2010 it kind of works but some stuff still seems broken:
1. I need to turn on IIS 6 Compatibility on a Win 2008 R2 box to get the msi to run.
2. The msi includes web.config, web.debug.config, and web.release.config. I thought VS's web.config transformations was supposed to take care of that.
-Matt
I suggest looking at using MSDeploy, which packages up all your files and configuration settings into a zip file that can then be imported into IIS 7.
Scott Hanselman had a great presentation that shows how to use MSDeploy.
What's the minimum that I need to have installed on my Build Server (in addition to the standard .Net 3.5 stuff) to allow it to compile Silverlight 2.0 applications?
I have a Silverlight application that seems to be building correctly, but is not playing nicely with a related Web Application project - see this related question that I asked earlier: Silverlight xap file not being copied to ClientBin on Build Server
AFAIK you need Microsoft Silverlight 2 SDK to install on the build server.
HTH
Your build server should be pretty much an exact replication of your development machine as far as plug-ins, assemblies, run-times, SDK's etc.
You build server will be building your app via MSBuild.
In your particular case I suspect that you need to install the Silverlight Toolkit. This will give you the SL development runtime and the appropriate project build requisites for your XAP files to build and be deployed properly.