I've done a simple application using Asp.net MVC 5.
Are there any ways to deploy my application from Visual studio to Heroku ?
Can anyone instruct me please ? I'm new to open source servers.
Thank you :)
Heroku doesn't officially support ASP.NET, nor am I aware that there are any plans to do so. That being said, there are many OS buildpacks that you might be able to leverage to deploy your application. This one is a little stale but you could give it a shot.
Another option would be to fork the buildpack above and suit it to your needs.
Related
AppHarbor supports Node using iisnode. Can I deploy my Sails.js app to AppHarbor at this time, and if so, how?
I honestly have no idea what I'm doing with a node deploy but I'm trying to follow along with what I'm reading online. When I deploy my code out to my repo and AppHarbor builds it I get the following error: The current identity (...) does not have write access to 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files'.
UPDATE (September 2013)
There is an updated deployment guide here:
https://github.com/balderdashy/sails-wiki/blob/0.9/deployment.md …
#chadn posted an example Heroku deployment with Sails.js here:
https://github.com/chadn/heroku-sails
Original post
I don't know a whole lot about Windows deployments in general, but we do have a deployment guide here:
https://github.com/balderdashy/sails/wiki/Guide:-Deployment
Also, I know the guys/gals at Nodejitsu and Modulus have helped out folks getting their Sails apps set up, so that might be a good place to start as well.
Good luck!
i am interested in creating a setup tool for our business application which is based on a Windows Service and some WF4 workflows, currently hosted in IIS/AppFabric.
As long as i want to provide the best possible installing experience to our customers, I want to include IIS and Appfabric Setup Prerequirements as well as a WindowsService application into one Application-Setup Project.
Is there a proper way of doing this? Can someone give me some Links and/or Tips?
best regards,
Chris
The standard approach is to build a Deployment Package and import that into IIS. Is uses Web Deploy, see http://go.microsoft.com/?linkid=9278654 for more details.
For client deployment using a setup project, I've been a fan of using WIX and an automated build script (MSBuild or Nant) in the past. It allows me the flexibility to script the build of the setup.exe, allowing me to make the changes I need (connection strings) in advance of deploying; leaving the entire process (regardless of environment [dev, prod, QC]) scriptable and automated.
For deploying the workflow components, its as simple as xcopy deployment which, like the above, is easily scriptable and automatable.
Our main application uses Commerce Server 2002, we are currently in the process of upgrading to 2009. I am looking into setting up CC.net for both apps. I have it pulling from SVN and starting the build but it will fail because Commerce Server is not installed so the DLL's are not there.
I don't really want to do a full install of Commerce Server on the CI Server if I can avoid it. Does anyone have any experience / advice on setting up the CI Server / repo / project so that It would build without CS installed. currently we do not have any unit tests so that part is not an issue, its getting it to build and being able to do things like FXCop, etc.
Thanks
As far as I can see, there is no problem in put just the core DLLs of Commerce Server in a "References" directory created under the same structure of your source code.
I have been using this approach in many projects without problems so far.
Maybe, the only problem you'll have now (since you are not using this approach) is that you'll need to refactor a bit your solution to put the references.
Regards,
Alex
I have a private .NET (C#) project using Git Repository in Unfuddle.com. I wish to utilize a hosted Continuous Integration tool like CruiseControl.Net. Can anybody recommend a hosted CI solution, that can integrate with Git and is reliable and cost effective?
Thanks.
Found projectlocker.com but don't know anything about them.
I will say though, that setting up your own CI server is fairly simple and will probably only take you 1 day to setup for your projects.
TeamCity works great with C#\Msbuild and is free of charge up to 20 developers.
fazend.com offers a free hosted CI service, but only for Subversion at the moment.
I have a number of asp and asp.net 2.0 applications that I need to move to a new Win2003 server.
I've created a test suite to verify that different aspects are installed and configured properly, but other than exporting the IIS metabase from the two servers and comparing manually, are there any tools or techniques I'm missing?
The Microsoft Web Deployment Tool should allow you to do pretty much what you want.
From the linked web site:
The Web Deployment Tool is a tool for simplifying the deployment, management and migration of Web applications, sites and even entire servers. Developers can package a Web site, automatically including content, configuration, certificates and databases. These packages can be directly deployed to a server or packaged and shared with others. IT Professionals can enable developers to deploy these packages to a server and delegate access to non-admins. IT Professionals can also use the tool in their infrastructure to synchronize servers easily on both IIS 6.0 and IIS 7.0, or even to accomplish a migration from IIS 6.0 to IIS 7.0.
When it comes to metabase edits, it allows you to easily get a list of all settings your site is dependent on, and sync these to the target server (complete with a handy 'what if' mode).
What version of IIS? (This will impact the extract steps.)
You can export settings from IIS manager and import.
If you're doing it manually then I'd use something like BeyondCompare to make your life easier.
You could write some code using System.DirectoryService to programatically compare the two servers settings, or compare a given server against an Xml file have a look at this
Look at the sdc extensions for MSBuild they let you create websites in a msbuild file so if you can verify that you can create it correctly you can just add that to your build script.
To use move your application to another IIS.
1) First use ntbackup, and backaup
the applicaton folder.
2) Export the application
configuration to a file in IIS.
3) On the other server use the
ntbackup command and then restore the
files in the same path.
4) Create the application from the
config file.
5) Adjust possible missed
configurations.
6 That's it.
In our company we are migrating many .NET apps from our testing servers to productive ones, and we follow this guide.
Best Regards!