We have a TeamCity installation which we have just upgraded from 8.0.1 to 2017.1.1. Everything when very smooth and plainless.
However, we seem to have a problem with our agents, which SEEM to be slower now than before.
The current agents (all virtual on an inhouse VMWare ESXi 6 server) are running Windows 7 32-bit and has not been re-installed or undergone significant maintenance in more than 6 years. I was not the one to do the original installation, so I do not have the full history of the agents, although it is close.
In the beginning the access to the agents was somewhat of the wild west, and thus they are not as alike as I would like.
So, I am thinking of creating new agents and replace the old ones, but am having some questions regarding this.
We develop almost exclusively in .NET with a few licensed third-party products, so the setup of an agent should be relatively simple. We do have a few legacy .NET Compact Edition 3.5 builds, but otherwise it is more or less regular Visual Studio solutions ranging from .NET 3.5 to 4.6. Many solutions are Silverlight.
I am aware of the issue with the missing Microsoft.WebApplication.targets without Visual Studio installed, and have no problem with manually copying the files.
I am thinking about basing the agents on Windows 10 64-bit, but would it be better with 32-bit?
I intend to install the following packages, at least:
.NET Framework 3.5 (Optional Windows component on Windows 10).
.NET Framework 4.6 (Default Windows component on Windows 10).
Windows SDK 7.0
Windows SDK 7.1
Windows SDK 8.0
Windows SDK 8.1
Windows SDK 10.0 or 10.1.
Microsoft Build Tools 2013
Microsoft Build Tools 2015
Microsoft Build Tools 2017
Silverlight 5 SDK
Power Toys for .NET Compact Framework 3.5
The two Windows component should cover .NET 2.0, 3.0, 3.5, 4.0, 4.5 and 4.6. But will I need to install some or all of these separately?
How about 4.5.1 and 4.5.2?
How about 4.6.1 and 4.6.2?
Is there anything else, that I should be aware of?
Is it a good idea to use 64-bit agents?
Will there be issues on older target systems?
Any caveats I need to be aware of?
I hope someone will take the time to answer some or all of my questions.
Thank you.
Related
I want to start developing App for Windows Phone.
I have installed Visual Studio 2010 Express, Updating it to SP1. Install Windows Phone SDK 7.1. And when I want to create a new Project, here comes the error.
I have installed .NET Framework 3.5 to 4.5. Silverlight SDK 4.0. What am I missing here ?
I am using Windows 8 32 bit if it has any difference.
Microsoft made developing for windows-phone as complicated as possible. )
So, basically there are two solutions, that are guaranteed to work:
1) You can develop on Visual Studio 2010 for windows-phone-7 on Windows 7.
2)You can develop on Visual Studio 2012 for windows-phone-8 on Windows 8(64-bit).
The other variations are more like a 'dance with tambourine', in my humble opinion.
There are solutions, but they are all tricky.
What may work for you:
Check this question, maybe it helps.
The first answer has a link with instruction of how-to install a sdk for wp7 on windows 8. Try it. However, there's no mention about 32-it system, so it might also not work.
Right now, you've said, you've installed SDK 7.0. Try to to, as suggested in above-mentioned link and install Windows Phone SDK 7.1 and 7.1.1 update.
I have read that opening a vs2010 project in vs2012 is fine (as long as you are using VS2010 SP1) it will not update the project files and those on VS2010 SP1 will not have problems using it: http://visualstudiomagazine.com/articles/2012/03/01/more-power.aspx
However I have heard that the version of .net 4 is higher when using vs 2012 than with vs2010 (I don't mean .net 4.5 by the way). Is this correct and could it cause problems with a release on a development machine being tested against a different version of the .net 4 framework? It sounds a bit unlikely to me.
thanks
Adam
The answer is not simple. All the details can be found here
There are many different types of projects in VS, and some don't require upgrades, some are compatible but require upgrades, and some are simply not compatible. It depends on the project type.
Also, to answer your question about the .net versions, 4.5 is considered an "in place" upgrade. This means once you've installed 4.5, it replaces 4 completely. So, once you've installed 4.5 you use that any time you target 4.
Several bugs has been fixed with .NET 4.5, so suddenly you cannot reproduce bugs that people experience in live-environment (WinXP/Win2k3 - .NET 4.0), as your own machine that have VS2012 installed (.NET 4.5).
More Info If I target .net 4.0 but run on a machine that has .net 4.5 will .net 4.0 WPF bugs still be there?
More Info Make VS2012 not hide .NET 4.0 bugs when targeting .NET 4.0
More Info Support a .NET 4.0 Service Pack on Windows XP Supporting those .NET 4.0 Bugs Fixed in .NET 4.5
I have a Windows 7 machine and I see that Microsoft does not recommend Visual Studio 2003 on the computer (Windows 7). How can I develop an application for the .net framework 1.0 then? I currently have visual basic express 2010.
EDIT: 1.0 runs on older machines that require administrator to update.
VS 2010 will only let you target back to 2.0 Framework. You can either put XP on your development machine, or use a virtual machine with XP to put VS 2003 on it.
There seems to be a way to do it. It does not seem to be supported but you can give this a try.
Installing 1.X Framework on Win7
Does anyone know if there is an SDK for the .Net 4.0 framework, and if there is one, where does the installer put it on the hard drive? I've installed the Ultimate Edition of Visual Studio 2010, but can't find the SDK anywhere.
The last stand-alone version of the .NET SDK was 2.0. It got integrated with the Windows SDK after that. You already have the important bits on your machine, it is stored in c:\program files\microsoft sdks\windodws\v7.0a
It is a truncated version (thus the "a"), the full version is a separate download. Beware that this download is 7.1. There have been a fair number of critical problems with the version 7.0 SDK installer btw. The install failed on my machine, leaving a partial install that didn't rewind. I had to patch registry entries by hand to recover. I recommend you install this on a non-critical machine and just copy the folder. I had no trouble with the SDK 7.1 installer.
Microsoft Windows SDK for Windows 7 and .NET Framework 4 (ISO)
Microsoft Windows SDK for Windows 7 and .NET Framework 4 (Web)
These links point to the Version 7.1 of the SDK.
%ProgramFiles%\Microsoft SDKs\Windows\v7.0A
I have a machine with Vsiual Studio 2005 and Visual Studio 2008 and Windows SDK version 6.1 (Windows Vista). I am planning to install the latest SDK (Windows 7 and .Net 3.5 Service Pack1), but the MSDN Comptabilty document (http://msdn.microsoft.com/en-us/windows/dd146047.aspx) indicates that the latest SDK is not recommended with VS 2005.
I would like to check if the two SDKs can coexist on the same machine or the latest SDK will oevrride the older version and could cause issues with VS 2005.
Thanks
Just a word of warning, the 7.0 SDK has a badly broken installer. It hacks registry keys that are used by Visual Studio to find SDK components and drops files in the VS install directory. This can render it unusable. The worst problems are documented as sticky posts in the Windows SDK forum at the MSDN forums.
I had problems as well, the installer failed half-way through on my machine with a completely undescriptive error. On a pretty virgin machine with VS2008. It didn't roll back the install even though it failed, I had to edit the registry by hand to fix the damage.
I recommend you actually install the SDK on a machine you don't care about. Then copy the directory to a production machine and edit the VC++ directories yourself. Do strongly favor the v7.1 version instead. Good luck with it.
Should be fine as long as you don't try and install both versions of Visual Studio in the same folder. The SDK is essentially passive, you can have as many of them as you want installed, but you need to make sure that the paths that VS 2005 uses are to the older SDK rather than the newer one.
Since by default, the SDK is installed in a subfolder of the Visual Studio install folder, a long as you put different versions of VS in different folders, everything should work out fine all by itself.
Yes they can. I have 6.1 and 7.0 on one machine (Windows 7 64 bit no VS 2005 though) without any noticeable issues.
Definitely you can . u can set the sdk version u want to use each time .
This links tells how to set up your sdk versions in different visual studio versions.
http://msdn.microsoft.com/en-us/library/ff660764.aspx