Trying to build and publish asp.net(Not Core) application using aws CodeBuild.
Does aws codebuild support traditional .net application?
Gone through older thread on stackoverflow but still not clear.
Tried with sample asp.net application on aws Codebuild, it's able to build but not able to Publish and get all the artifacts i need to deploy on IIS.
Anyone tried aws codebuild with asp.net application?
This question sounds silly but having hard time publishing asp.net application using codebuild. Tried most of the MSbuild command given for this online.
Yes, CodeBuild supports .NET Framework applications, please refer to the following link which is a tutorial:
https://docs.aws.amazon.com/codebuild/latest/userguide/sample-windows.html
... and the following blog post:
https://aws.amazon.com/blogs/devops/creating-ci-cd-pipelines-for-asp-net-4-x-with-aws-codepipeline-and-aws-elastic-beanstalk/
Excerpt of configuring CodeBuild project:
After choosing Next, select AWS CodeBuild as the build provider.
Select your region, then choose Create project, which will open CodeBuild in another browser window.
In the CodeBuild window, you can optionally assign your build project a name and description.
Under Environment, select the Custom image option, and select Windows as the environment type.
For building ASP.NET 4.x (.NET Framework) web projects, it’s easiest to start out with Microsoft’s .NET Framework SDK docker image,
which they host on their registry. Select Other registry, and use
mcr.microsoft.com/dotnet/framework/sdk:[version-tag] as the registry
URL. Replace version-tag with the .NET framework version. For .NET
Framework 4.x, the most likely options are 4.7.1, 4.7.2 or 4.8. This
example uses mcr.microsoft.com/dotnet/framework/sdk:4.7.2.
Related
Is it possible to do a self contained publish for an ASP.NET Core 2.0 app to Azure?
I use the following command line approach to create a publish folder of my WebJobs project and I really like this approach because it gives me full control.
dotnet publish --self-contained -r win10-x64 -c Release
Can I use the same for my ASP.NET Core 2.0 app? It's important to point out that I have a React frontend. I do, however, manually prepare the frontend files using Webpack.
Currently, I publish the ASP.NET Core app from Visual Studio and I can't say that I'm happy with it. It takes too long and I frequently get errors. I'd much rather go with the self contained publish approach.
You could use self-contained deployment to create a publish folder of your Asp.net core in local folder.
Is it possible to do a self contained publish for an ASP.NET Core 2.0 app to Azure?
I think you would publish all the app files in \bin\Release\ to azure app service.
If so, you could try to deploy the application using Git.
In my VS(2015) solution, I have a ASP.Net website and a WebAPI project. For normal development, I want to use IIS on local machine for dev/test. However, I also want the option to be able to deploy the same sites to Azure on demand.
I know I can 'Convert' an existing project to Azure project from VS. But then it'll become a cloud project only. I don't want to convert it to cloud project.
Is there a way I can use my existing projects in VS and deploy/publish them to Azure?
Thanks
You don't need to "convert" your project to an Azure project, you can simply create a publishing profile in Visual Studio and push the build to Azure.
The Microsoft documentation explains how to do this, follow the steps from the "Publish to Azure" section onwards.
In this video, Scott Hanselman interviews a guy from the ASP.NET team. He says that one of the goals of ASP.NET 5, on top of .NET Core, is that the apps won't depend on the .NET Framework and GAC assemblies on the hosting server. Instead, .NET Core libraries will be released via NuGet packages and apps will be deployed with their dependencies.
One of the reasons for this is so Microsoft can quickly release a bug fix or new feature, and we don't have to wait until the new version (of the full framework) is installed on our hosting environment.
My question is:
Are the apps built on .NET Core really independent of the version of .NET installed on the target machine, and can they run even without the .NET Framework installed?
Yes, the framework you use in your application is completely independent of the .NET Framework installed on the target server, because the Core .NET Framework is referenced via NuGet packages and can be bundled up for deployment via the DNX Utility, specifically of interest to you will be the dnu publish command.
Here is an excerpt, describing what dnu publish does:
Publish (dnu publish)
The publish command will package your application into a self-contained directory that can be launched. It will create the following directory structure:
output/
output/packages
output/appName
output/commandName.cmd
The packages directory contains all the packages your application needs to run.
The appName directory will contain all of your applications code, if you have project references they will appear as their own directory with code at this level as well.
So the .NET Core will exist in the output/packages directory and will not need to be installed on the target server.
A normal .net core app requires that you install .net core on the machine you wish to run the application on. There is a way to avoid this however, by publishing a self contained app. You can publish your app with the requisite version of .net core included. This will make your app larger, but if you only need one application on a machine to run .net, you need a specific version of .net, or you want to make a portable application, this is a good choice.
I have an ASP.NET Web API project created on Windows using Visual Studio. How can I set this up for use with DNX/DNVM (on a Mac)?
Switching to Git solved the source control compatibility with TFS. But I wasn't able to find references to getting a project working across both these development environments.
I'm assuming as a first step the project will have to be migrated to ASP.NET 5/vNext but wondering other problems lurk around the corner with different project members using different environments.
I get an error when I run - git:(master):dnx . kestrel
As you mentioned yes you will have to migrate any namespace changes. I have a project that is developed across both. Also changing csproj files to xproj. Support is coming for some kind of interop between the different project types but its not here yet.
For build, publish, deploy from git without relying on VS publish capabilities or MSBuild you can follow my blog post here.
Basically you use DNU to publish and then kudu to deploy.
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.