I am attempting to use a build project to publish files from TFS to our web server. I don't have a project file as these are html, text, js files managed outside of Visual Studio. The basis for my attempt was How do you include additional files using VS2010 web deployment packages? and while the status of the build is successful, the files never get published to the server. Has anyone every used Web Publishing to push files maintained in TFS to a server like this. I want to use the standard publishing targets so the builds are easy to maintain ongoing.
I think the tooling in Visual Studio that builds Web Deployment packages requires a Web Application Project.
I suggest creating a Web Application project and adding your html/js files to it, then the default publish targets should be able to build a web deploy package and publish it without problem.
Related
I'm publishing my application to two separate IIS servers. The problem I have is when publishing to profile01 it builds the project and then publishes successfully. I then Publish again but switch to profile02. Upon doing this it builds the solution again (changing assembly version #) and publishes to the other server.
Now I have mismatched versions between server 01 and server02.
I'm assuming that when I change Profiles it makes a change somewhere to the project, once that change is made VS assumes a new build is required.
Any thoughts, suggestions, references would be greatly appreciated.
You can create a Web Deployment package & deploy this package to multiple servers. Documentation on how to create and deploy using the package is available here - https://msdn.microsoft.com/en-us/library/dd465323(v=vs.110).aspx
My VSTS Repository contains 50+ Visual Studio projects of Azure Web Apps and I was requested to get an automated build and release process in place for one of them. I went thru and selected a Visual Studio template and on the build solution I selected only the one project I wanted to do a build and release on but when I queue the build to run it starts doing a get latest on every project in the repository. This is unacceptable because it would take hours to get latest on all the projects just to compile and publish one website. This makes no sense to me. Is there a way to limit what the build does a get latest on?
Depends on the repository type you're using. In case you're using TFVC, you can go to the Repositories tab and configure your workspace mappings to match exactly what you need for your project.
If you're using Git, then you're out of luck, the way git repositories are synced, the whole repository is always fetched when a build is initiated.
If you're using your own build agent, you can configure it to retain the sources directory, in which case only the differences are synced when a build runs.
I have an MVC app in VS2013, and it has several related web/service projects, and one console app that is used for running SQL scripts against the database (it uses DbUP, to integrate with Octopus Deploy).
How can I generate NuGet Packages for both the web app and the console app?
I have created a separate Visual Studio (sln) step to build this project, but I get a missing reference error for the DbUp NuGet package. If I add a project reference to the web app, then the build is successful, but no artifact is generated. I would like to generate the NuGet package without adding the reference.
Well, this is embarrassing. Adding OctoPack NuGet package to my console app solved my problems.
How to use TypeScript for Mobile Services scripts (with node.js backend)?
Is there a definition file for Mobile Services? (on the server, not on the client!)
And how about the tooling?
Sure, I can open the scripts in Visual Studio 2013 via the Azure node in the Server Explorer, but than they are not part of a Visual Studio solution. How to add a definition file via NuGet in that case?
If you enable source control on your mobile service, you can upload your scripts via git. This would enable a workflow where you write your scripts in TS, run the compiler to output JS, and you commit the generated js files to your repository and push them to the server.
Unfortunately I do not have any advice regarding tooling support.
You can use the TypeScript definition here: https://www.nuget.org/packages/azure-mobile-services-client.TypeScript.DefinitelyTyped
I am new to sharepoint and installshield. My responsiblity is to build and deploy the sharepoint solution as a package using istallsheild. Previously I was using solution package wsp and content database restoration. But now the client wants to deliver the total solution i.e. dlls, ascx files, xml files, servce files(.cs), feature files using installsjield from development server to another (test and/or client) server.
Can any body help me on this: how to do the sharepoint deployment using installshield?
thanks in advance.
I presume you are using SharePoint solutions to package dll's, ascx and xml files for deployment to a sharepoint server. These solutions are built using a tool like WSPBuilder.
If not: YOU SHOULD!
If so: Why not use SharePoint Installer? It is an installer wrapper around a .wsp (SharePoint solution) file. It will check for the existence of a sharepoint installation, if the required services are started etc.
For deployment to a test machine: Why would you need the .cs files? If you want to test (debug) code on a test machine, I suggest you use either continuous integration using a tool like CruiseControl.NET, or just install Visual Studio on the test machine (which I presume to be a dev test, not a client test machine) and get the latest version, do a build, then roll out the solution.
And what do you mean with "client" server? is there some windows app that's communicating with sharepoint included in the installer? If so, I suggest separating the SharePoint solution from the actual windows app. They might share DLL's but are not supposed to be in the same installer.
We are using a tool (open source - saf.codeplex.com) to automate the Sharepoint components using MSBuild/Features/STSADM etc. Recently they have upgraded this to use WIX so that we can deploy any SharePoint components.
saf.codeplex.com
It has got an very good documentation and also we got a good support in fixing and implementing the SharePoint automated deployment in our premise.
Thanks
BalamuruganK