I was trying to install visual source safe 2005 software in windows server 2016 , I am getting compatibility error. As shown in the below image .
Just wanted to check if VSS 2005 is compatible with windows server 2016 or windows server 2012.
Related
As per the information published for Microsoft Visual C++ Redistributable 2013, Windows 2012 R2 is the latest platform supported on Windows Operating systems.
Our application code (C++) is built with Visual Studio C++ 2013 and we are using VC++ redistributable 2013 on Windows 2012 R2 platform to work with the binaries which are built as mentioned above.
Now, we are planning to use VC++ redistributable 2013 on Windows 2016 platform to work with same binaries. When I check for platform support of VC++ redistributable 2013 for Windows platforms, Windows 2012 R2 is the latest platform supported and I dont see Windows 2016 is mentioned in the supported platforms list. (Ref: https://msdn.microsoft.com/en-us/library/ms235435(v=vs.120).aspx)
When I test internally with VC++ redistrbutable 2013 on Windows 2016 platform, binaries are running good as expected as of now.
So, I am assuming VC++ redistrbutable 2013 supports on Windows 2016 platform.
Can you please provide confirmation on support of VC++ redistrbutable 2013 supports on Windows 2016 platform? So that, we can use our application on Windows 2016 platform using VC++ redistrbutable 2013.
If these are any published KBs for support of VC++ redistrbutable 2013 on Windows 2016 platform, Please share.
Please provide confirmation on support of VC++ redistrbutable 2013 on Windows 2016 platform.
If I understand the table you link to correctly, it specifies for which platforms you can build software for with the given Visual Studio version. This does in no way imply that the software so built does not run on more modern platforms.
Typically, the opposite will be the case: Old software will run on modern platforms. That's called compatibility. I do not think that Microsoft will decide to break (moderately) old software wholesale and intentionally.
We actually have a Windows Server 2008 R2 with Team Foundation Server 2010 installed, which has a projectcollection configured. A databaseproject was migrated from Visual Studio Premium 2010 to Visual Studio Premium 2012 and checked in to TFS2010.
On another Windows Server 2008 R2, Team Foundation Server 2010 is as TFS Build Server with Build Agents installed [TFS2010 Server with projectcollection and TFS Build Server 2010 works fine together].
After migration of databaseproject from Visual Studio Premium 2010 to Visual Studio Premium 2012, TFS Build and Deployment does not work, because on TFS2010 Build server, .deploymanifest file was used. But now for dbproject in VS2012, there are fewer files with .dacpac files.
I was reading a lot about compatibility and there is different information about executing db project build and deployment form VS2012 on a VS2010 TFS build server.
If I deinstall TFS2010 build server and installed TFS2013, at this point to select the project collection on the TFS2010, there will be shown an incompatibility error.
Is there an solution where we can build and deploy a VS2012 db project checked in TFS2010 from VS2012 on a TFS2010 or TFS2013 build server?
When linking a TFS Build server, the version of the build server must always be the same or older than the TFS server, so the following is possible:
TFS Server version | Supported Team Build versions
2015 | 2010 SP1+CompatFix, 2012, 2013, 2015
2013 | 2010 SP1+CompatFix, 2012, 2013
2012 | 2010 SP1+CompatFix, 2012
2010 | 2010
When installing a newer version of Visual Studio on the build server, you can use its tools to build the code, but you need to make sure Team Build is using the correct version of MsBuild.exe. The executable is installed in a different path since .NET 4.0 was introduced:
MsBuild version | Path
4.0 (2012, 2010) | C:\Windows\Microsoft.NET\Framework\v4.0.30319
12.0 (2013) | C:\Program Files (x86)\MSBuild\12.0\Bin
14.0 (2015) | C:\Program Files (x86)\MSBuild\14.0\Bin
Some features only work when the version of MsBuild is used which supports the feature.
The "Run MsBuild" activity in your XAML build workflow has a property called ToolPath, setting this to the correct path. It also has a ToolsVersion property, which you need to set to "11.0". This seems only required when using a version of the tools is newer than the version of the build engine.
Important note: TFS 2010 has reached its end of the support lifecycle last July. It may be a good idea to upgrade the server to a supported version.
I am wondering how we are suppose to use the remote debugger on a target machine with Windows XP for applications build using Visual Studio 2013.
It seems that Remote Debug Tools for Microsoft Visual Studio 2013 (and 2012) do not install on Windows XP, complaining that they need a newer Windows version. Microsoft download do not say a thing about requirements.
I guess there should be a way of doing it...
Here is the document on Visual Studio 2013 Compatibility and it does state that Remote Debugging and profiling tools are not available for the targeted platforms of XP and Vista.
Most likely the reason that the Remote Tools for Visual Studio 2012 and 2013 do not run on XP is that XP does not support .NET 4.5.
Target your app for .NET 4 so you can run it on the XP platform, and use Visual Studio 2013 to do the majority of the coding and then use Visual Studio 2010 to do the remote debugging when needed. VS 2010 and 2013 can run side by side and the project formats are compatible so you should be able to go back and forth very easily.
I installed VS 2012 Express and then later installed MS SQL Server 2012 Express with Tools.
Oddly, I now have two Visual Studio IDE's: the 2010 version that works with MS SQL Server 2012 projects and the 2012 Version that works with c#, vb, C++ projects...
How can I get the MS SQL Server projects to show in VS 2012 alongside c#, vb and C++ ?
Wait until 2013 comes out? They're behind on SQL Server Management Studio and VS, kind of how Visio was behind when the Office Ribbon came out and how Office was behind when Windows 8 came out.
Can I use the Visual Studio 2010 remote debugger on Windows XP to debug a .Net 4.0 app from Visual Studio 2012?
I am trying to, here is a screenshot of my XP machine (I have disabled the local firewall temporarily):
Here is Visual Studio 2012 (the text in the remote machine box is identical to the server name indictaed by the Visual Studio remote debugger):
When I try to debug, I get this error:
If I change the computer name to anything else, I get this error:
Is being able to debug .Net 4.0 apps remotely from Visual Studio 2012 on Windows XP wishful thinking on my part or should this work?
Just to give some background, we have some .Net 4.0 code running on Windows 7 ok, but crashing under XP. I understand that the .Net 4.5 compiler is an in place upgrade of the 4.0 compiler, and if you have a bug in .Net 4.0 which has been fixed in 4.5, your 4.0 code will compile fine because you are using the more up to date, fixed compiler, but you may get runtime issues on actual .Net 4.0 machines. I suspect this may be the case and wish to test it out.
And we have to use Visual Studio 2012, I don't make the rules!
The MSDN blog tells us (2012 Oct 8) that there is no support for remote debugging from VS 2012 to XP:
Remote Debugging
The Remote Tools for Visual Studio 2012 do not support remote debugging on an XP client. When debugging on Windows XP is required, it is recommended to use the debuggers of an older version of Visual Studio, such as Visual Studio 2010, for local or remote debugging. This is in line with the Windows Vista experience for Visual Studio 2012 RTM, which is a runtime target but not a remote debugging target.