Actually i deploy my asp project using Plesk. My project in testing phase so the client ask for some changes in project. The changes are related to a particular page but after changes i deploy all publish files of my project, which is so time consuming task. Is there is any way to deploy only the particular page from my project.
Thanks....
#Shahid bro, a possible solution can be to use FTP client to upload individual files.
Related
For a long time I have been performing dated deploys to our IIS servers, basically this means that each deploy gets its own dated folder within the web site folder (c:\sites\my-site\20140824-1236 for example). I then redirect the web app to the new deployment folder.
This gives us a quick role back capability if things go pear shaped.
The problem is that we are looking at moving deployment over to the new web deploy techniques, while we have been using the new techniques within QA and UAT for a while - the standard behaviour is to simply replace the files at the location defined within the IIS web site.
Before I go and start looking at remote PowerShell to re-configure IIS before executing the web deploy.. does anyone know how I can achieve this using standard web deploy.. maybe with msbuild extensions or something?
How about using the automatic backup capabilities in Web Deploy v3?
http://www.iis.net/learn/publish/using-web-deploy/web-deploy-automatic-backups
So I'm using visual studio 2010 to build a website that was formerly running on PHP, so I'm pretty new to the environment.
In starting the project I built a website project, not a web application project. I know that will probably generate a lot of "never use a website project, use a web application project instead" comments, but bear with me.
I'm attempting to provide our server team with the necessary files to compile on our server for the first time. However they're used to working with web application files, not website files.
Normally they are given the source code and a batch file that compiles the code into deployment directories and then they just move the files to the server from there. I'm pretty sure that the other teams use deployment packages to do this, which obviously isn't an option for a website.
My question is, what would be the equivalent steps for getting the source for a website ready to deploy vs a web application? I have published the website to a separate folder and this has rendered what I think is the equivalent in many ways, but I wanted to make sure.
Also, is it possible to publish certain parts of a website without others?
Please with-hold all the comments about how I should be using a web application instead, google seems to assume that's all that's used out there too.
Thanks!
There isn't much to deploying a web site other than copying the source files to a directory in IIS. It will compile the site automatically on the first page request.
I agree with Britton. I personally prefer web application but with the web site project you have 2 options.
Either a) Upload all the files (including the .vb or .cs files) and the web server will compile on the fly. OR, you can publish to a separate folder locally on your machine, and then upload that folder. I would do the publish if you don't want anyone seeing your source code.
i am looking for a way to autodeploy a Dot Net Nuke website by TFS after checking in. I also need to some how transform web config to the right connection for the deploy server.
Since this is a website but not a web application, thing becomes tricky. If you have done it before, please give me some idea.
Thanks
I have not done auto deployment with TFS but did automate the process with SVN. What we did is simply have the script deploy everything that had changed since last login to the web server - EXCEPT - the web.config.
Database scripts were handled by a process like this but those were not as reliable as the SVN code deployment was.
HTH
You could use a deployment tool such as kwatee (self promotion). Kwatee is configured via a web GUI and can then deploy any application or site via python scripts and transform files along the way.
You can use Visual Studio web deploy feature. ALM Rangers shipped a ready to use BRDLite Reference template for this purpose which you can download here. Also, check this link for documentation for the template usage.
If you're using VS2010, you can use a Web Deploy Project in your solution. TFS will talk to the WDP as it would with a web application's project file.
For config transforms, you can use a tool called SlowCheetah.
I want to know a few things about Publishing an asp.net web application,
Why should i publish my web application?
What are the advantages of publishing a web application?
1- if you want to crypt your configuration settings you should publish. http://msdn.microsoft.com/en-us/library/53tyfkaw%28VS.80%29.aspx
2- first if you just copy your web site to your IIS it will compile first then starts serving. publishing wins that compile time. second if you want to send just dlls to your server it will be easier to deploy.
my personal opinion if you are the only developer on the project and you may need to change stuff on an editor like notepad and deploy ASAP then dont do it.
but if you have a big team and timeline and deploy is a one of a big issue for project. you need to do that to keep track.
You should use web application because of the advantages of Web application. :-)
I think web application has some advantages:
Web application will be compiled before published, so the code will be checked by compiler.
One web application(project) has only one DLL file.
use dll file and not use source code
can encrypt file
I want to lock down my website so that the end customer cannot change the standard web pages(aspx). I have investigated code signing and digital certificates. But that is more suited for the dlls and executables, and not to the aspx/html pages themselves. Is this possible? If so, please provide me some links.
Thanks,
Murali
You can precompile your ASP.NET application.
"When you precompile an ASP.NET Web site for deployment you create a layout containing assemblies and other information that you can then copy to a production server. A Web site that is precompiled for deployment gives you the ability to create a compiled version of the site that can be deployed to a production server without source code."
http://msdn.microsoft.com/en-us/library/ms227976.aspx
Have you looked into providing your application as Software as a Service (Saas)?