I am using Windows server 2003 OS.I have built SharePoint webparts in VS2010 for SharePoint 2007.Each time I deploy from the WSP project it takes few minutes to deploy it to the SharePoint site. This is considerably annoying since each time when the webpart code is changes it will take lot of time to deploy. It become very hard for the development and testing purpose.Can anyone suggest if there is any way to make the deployment faster?
Thank you
Consider deploying your web part to the bin during your dev process (using a post build xcopy or something similar). It'll speed you up massively. You'll still need to test your WSP deployment.
Related
It appears a fair number of release management deployment tasks and templates are not in TFS 2015 on premise right now, and I'm trying to figure out if this is by design or if my installation has problems. For instance, I do not have a sql deployment task available to me. I haven't been able to find confirmation one way or the other, so does the on premise version just not have these tasks?
be aware that VSTS development is always some months ahead of on-premise TFS. Especially release management is quite new and many enhancments and tasks will probably find it's way to TFS. Either directly, as extension or you can create custom tasks by yourself.
As seen here:
https://github.com/Microsoft/vsts-tasks/issues/1674 it's a very young step and all you need to get it work on your local TFS is on github:
https://github.com/Microsoft/vsts-tasks/tree/master/Tasks/SqlServerDacpacDeployment
This is by designed. It seems you are using some Extensions. You can find this in available extensions on the right top of the web portal.
Then you can find those tasks in below page and just need manually install the tasks.
DacPac deployments are part of the extention "IIS Web App Deployment Using WinRM"
https://marketplace.visualstudio.com/items?itemName=ms-vscs-rm.iiswebapp
Download and install it on your TFS server. You need to have Windows Remote Management enabled on your database servers for it to work.
I found this web site useful in getting it setup on the database server
http://www.hurryupandwait.io/blog/understanding-and-troubleshooting-winrm-connection-and-authentication-a-thrill-seekers-guide-to-adventure
I am using Visual Studio 2012 Professional to deploy my ASP.Net MVC website.
The problem is that when I use the one click publish feature, my web application comes to a screeching halt and it takes about 5 minutes for the website to respond normally again.
What are some things I can do to speed up this process to reduce or eliminate the amount of downtime for my users?
I publish to a separate copy of the site on the live server and I have a script which I then run on the server to compare the live site with the copy and only update new/changed files/directories and delete removed ones. This cuts down the downtime quite a bit, especially if there have only been minor changes.
I have a solution with multiple C# projects linked to a Website (File => New => Web Site).
I can use the continuous integration for all the C# project for now.
I would like to try the website from a different solution just for testing:
I would like to know if the modification of an aspx or aspx.cs file will
rebuild all the solution/project or just push the file which was
modified on Azure.
It seams that the website will be rebuild, or will try to rebuild.
Here is my website test solution
and my Build Definition file :
So my question is, is it possible to integrate a website to a continuous integration system ? (TFS 2012)
If it's possible, What did I miss on the basic configuration ?(I didn't need any specific configuration for a WebApp project or a C# project)
I might need to build some files on the website (App_Code folder), But I would keep the possibility to deploy only the modified files (aspx, aspx.cs) without rebuild all the website and push everything on the server.
Let me know if you need any further information
There is an article here Continuous Deployment di Asp.Net web sites con TFS Build. It is in italian, but I think you may get the core using Bing/Google translator.
I'm trying to put together an automated deployment strategy for my company's .NET application. We are using TFS/VS 2010, along with IIS for application hosting and msbuild for continuous integration & deployment. The application consists primarily of two components:
* A webapp
* A database
Our branching strategy, for the moment, is single-stream. That is, we have one big 'ol trunk, and for now we can assume that it will remain that way.
We've figured out how to get msbuild to deploy the webapp to IIS, so that's cool. Now I'm trying to figure out the best strategy for handling deployment of the database component. Right now, database deployment is entirely manual: our db architect builds the db on his machine periodically, examines the auto-generated migration script, and then manually writes pre/post deployment scripts. Then, he runs the whole deployment and sends an email to everyone.
This is not an ideal solution: the automated nightly webapp deployment works great, except when the dba fails to coordinate his manual db deployment work. This results in a lot of headaches for all parties. Thus, I'm trying to figure out how feasible an auto-deployment of the db will be.
I understand how to make msbuild deploy a database. However, the bigger problem seems to be properly managing pre/post deployment scripts.
With all this in mind, can anyone point me to best practices in this kind of a situation? I've done a lot of config mgmt in the past, but am new to managing a project with a database component.
we use the Visual Tool VSDBCMD to compare 2 databases and generating update sql scripts
http://msdn.microsoft.com/en-us/library/dd193283.aspx
I would like to hear the best practices or know how people perform the following task in TFS 2008.
I am intending on using TFS for building and storing web applications projects. Sometimes these projects can contain 100's of files (*.cs, *.acsx etc)
During the lifetime of the website, a small bug will get raised resulting in say a stylesheet change, and a change to default.aspx.cs for example.
On checking in these changes to TFS, and automated build would be triggered (great!), however for deploying the changes to the target production machine, I only need to deploy for example:
style.css
default.asx
MyWebApplications.dll
So my question is, can MSBuild be customized to generate a "code pack" of only the files which require deploying to the production server based on the changeset which cause the re-build?
You are probably going to have a hard time getting MSBuild itself to do this, but the ideal tool to use in your situation is the Web Deployment Tool, aka MSDeploy. With this tool you can tell it to deploy the changes to the target website. It will determine only the changed files and then just deploy those. Also you can perform customization to the deployment and a whole bunch of other stuff. It's a really great tool.