Where I currently work we are using TFS2010 and already have a build controller set up on a Windows Server 2008 R2 box. We are contemplating upgrading our TFS2010 instance to TFS2012, but in the meantime we are about to start development on a new product. The project team have established that it would be a good idea to create a new build server for this new product for the following reasons:
Our current products are .NET 3.5 solutions
The new product will be a .NET 4.5 WPF solution
Preference to install third-party components and tools required by the build of the new product in an environment separate to our current build server so as not affect the building and release of service packs and hot-fixes of existing products.
Can a TFS2010 build controller be installed on a Windows Server 2012 machine, and what are the things that I need to look out for? Or is it more advisable to install a new controller on another Windows Server 2008 R2 machine, and when we have upgraded to TFS2012 to upgrade the controller on the new server, and perhaps upgrade the server to Windows Server 2012 as well?
Installing TFS 2010 build controller in Windows Server 2012 was pretty simple. Note that .NET 3.5 needs to be installed on the build server before installing TFS 2010 build controllers.
Also if building .NET 4.5 applications, and are not keen on installing Visual Studio 2012 on a build server, the Windows 8 SDK should be installed.
Furthermore I would recommend installing MSBuild Community Tasks (https://code.google.com/p/msbuildtasks/downloads/detail?name=MSBuild.Community.Tasks.v1.4.0.56.msi&can=2&q=) for extra MSBuild functionality. This is especially beneficial for applying a version number to your assemblies by obtaining build number values from whatever automated build server technology you are using and supplying these values as parameters to MSBuild. The following article demonstrates this using the Bamboo CI server product: http://itrathnasekara.blogspot.com.au/2011/05/setting-assembly-version-automatically.html.
Related
I have had webdeploy running for YEARS on a Windows Server 2012 machine with standard MSBuild arguments (like this).
Yesterday I installed the Windows (Server Hosting) version of the .NET Core Installer from the .NET Core downloads page.
Since then my build tasks are running and successfully building my website, but not actually running any web deploy publishing. It is not failing - it is just not being run.
I want to stress I am talking about a 'legacy' .NET application - not a .NET Core application. I just installed .NET Core for somebody else.
I can verify this with the following observations:
There are no errors in any event viewers (except ones that are months old)
There is no message in the msbuild logfile that says Start Web Deploy Publish, however log files from just a couple days ago do have this message.
I can connect to the local server at port 8172 and it makes a connection.
It is happening with multiple projects that nobody else has access to.
_PublishedWebsites does get created with the latest files - it just never gets deployed anywhere.
What could possibly have broken this? Did the Windows Server Hosting package break it - or was it just some other update that came in? I've run out of ideas how to fix it and don't want to revert to xcopy!
Managed to fix it :-) Not sure exactly which of these steps did it, but I suspect it was Visual studio.
I was using TFS Express 2015 and upgraded to Update 3.
I also installed Visual Studio 2015 on the server itself.
I had previously had .NET Core RC2 (or whatever they called it at the time) installed and I uninstalled that before installing .NET Core RTM. Wondering if that removed some component that was required.
Like I said everything was working fine before I installed the .NET Core RTM - but fortunately installing VS and TFS brought everything back to normal.
I have a website developed using VS 2012 and created an MSI (Deployment Package) using the "Install Shield Limited Edition Project" available in VS 2012. While i am trying to install this application in a Win 7 system, it is creating a new AppPool as "ASP.NET v4.0 DefaultAppPool" and installing the application with this AppPool.
But if there are any previous application installed in the same system with the application pool as "DefaultAppPool", then my application's AppPool ("ASP.NET v4.0 DefaultAppPool") is getting applied for those previously installed applications (which has "DefaultAppPool" as its application pool) too.
Is there any settings that i am missing while creating the MSI using the Install Shield? Please advise on this
If you need flexibility in IIS installation the only serious alternative in my opinion is the open source WIX toolset.
I don't have time to write a proper answer right now, but please try these two earlier posts:
Wix generate single component id for entire tree
Warning in Wix Setup
Also check this post out to get an explanation of why WiX is best for this purpose. And definitely read the section on using dark.exe to decompile an existing MSI to get a WiX source file to start with.
So I have a suite of SSIS packages that we created using Visual Studio 2008 and are currently deployed on a SQL Server 2008R2 instance. However, I would like to upgrade these to 2012 via SQL Server Data Tools for Visual Studio 2012 which is easy enough, however, the company that I work for does not have any plans to upgrade the SQL Server to 2012 any time soon. So is there a way to create SSIS packages using SSIS 2012 and deploy them to a SQL Server 2008R2 instance while maintaining all of the new features of the SSIS 2012 package. IE Project Connection Managers and Package Parameters, etc...
Unfortunately, no. The Integration Services Service, the engine that which makes the package go, would have to be installed on the machine to be able to interpret/run them. Furthermore, unless you planned on running the packages from their .ispac containers, you wouldn't be able to take advantage of the rest of the "goodies" like the Environments, at least not without writing some ugly exec calls.
Also, if you think about slipping the IS services on that box, it is my understanding that's a SQL Server license consumed and given the ugliness that is the new per core licensing model on 2012, I wouldn't be happy writing that cheque. Not saying you'd do that, just a headache I saw at a client site when the auditors stopped by.
I recently setup a sharepoint server 2013 on our company and have found really good examples how you can override the suitbar with custom links.
Now that I'm trying to implement those examples i get to that point where Visual Studio 2012 and Office development tools is installed.
When i choose to start a new project I select New Project > Templates > Visual C# > Office/SharePoint > SharePoint Solutions > SharePoint 2013 Empty Project hit ok and i get an error that says Sharepoint not installed?
Am I supposed to install VS 2012 and develop om my Sharepoint 2013 server directly?
A very common way to develop SharePoint applications is to run a virtual machine (hyper-v under windows 8 for example) on your development workstation.
You can also dual-boot into a vhd file.
You can also install Windows Server 2012 and use one of the many desktop conversion techniques to use it as your primary operating system on your workstation.
Another often seen technique is to have a virtual machine hosted in the cloud or a datacenter, running both SharePoint Server and Visual Studio. Then connect to that machine using Remote Desktop.
With some trickery, you could have the SharePoint 2010 installer install om a workstation OS. This no longer works on SharePoint 2013. The reason this support was removed is due to the inclusion of Boot from VHD and Hyper-v into Windows 8.
It is my experience that if you just want to build your application and not run or debug it, that just having the assemblies copied over from an actual SharePoint Server will allow you to do that. I haven't found an updated document for SharePoint 2013 yet.
Yes. You have to develop on the sharepoint server directly using Visual Studio as Sharepoint server GAC has the required server object models to work programatically with sharepoint server object model.
You can aslo develop on client machine using Client Object Model or WCF Data Services Framework.
We would like to upgrade our clients to VS 2012 without upgrading the TFS server which is TFS 2008. Also, since we have several products, we want to modify the code to be C++11 compatible one product at a time. So the TFS server will have to support and issue builds for both VS 2008 and VS 2012 clients. Does anyone ever configured a TFS 2008 to work with two build servers? Is it even possible?