I am using Release Management Update 3 with TFS 2013.
I would like to upgrade to Release Management Update 4.
Questions
Do i need to uninstall and install new set up of RM update 4?
I have my release templates and other settings in my current version. How this upgrade going to impact on those things?
Any other challenges ?
Please share your thoughts/comments.
Yes, you have to uninstall the client and server prior to installing Update 4. It doesn't touch the database until you do the server configuration. It's just like TFS in that regard. None of your existing release templates will be impacted.
Update 4 adds very little in the way of new features for "classic" agent-based deployers; most of the new features are focused in the vNext release templates using DSC.
Related
Can I install Visual Studio Community Edition RTM and then Update 3?
Or, do I need to Install Update 1 then 2 then 3?
Yes, it is cumulative. Moreover, each time a new update is released, Microsoft immediately makes sure there is no access to any previous updates. All links to previous updates get redirected to the latest update. (More precisely, all links simply lead to the online installer, which always downloads the latest update).
This is a major PITA, BTW, since there's no immediate solution to new code-breaking bugs that Microsoft often introduces into new updates. Update 3 is quite problematic in that regard.
For this reason, if you already have Visual Studio installed, it is highly recommended to make a snapshot of your system before installing any further VS updates. That way you will always be able to revert to the previous version in case the new update is broken.
The VS install I downloaded (latest one) includes SP3.
So it appears that the current download of VS includes the latest SP updates.
I'm a new user into Team Foundation Server and I have a problem, during the develop an desktop app, a team member performed a inestable version and update (realize check-in) this version into the version control and the moment when I check-in my code the server merge my code with the latest version and the system failure.
I decided delete unstable versions of control version, but I not find way perform this.
I read this article but in the article only explain how to perform Roll back version and this does not help me.
You must do a rollback to maintain history of that change.
If you rollback the checkin out is just the same as if you had never checked that code in.
We have a number of Installshield projects that install and configure IIS applications. We have shipped several versions of the different applications (over 7 versions of 3 applications) and would now like to upgrade to use .net 4.0 instead of 2.0 & 3.5.
After modifying the "Internet Information Services" settings to change the ASP.NET Version on the web sites/application to 4.0.30319 and the .Net Framework version to v4.0 under the application pool, the installer correctly creates an application with the 4.0 version in IIS 6 and below, and in IIS 7 and above it correctly sets the pool to use v4.0, but upgrades do not work for any targets.
The upgrades install OK, but the .Net version of the virtual directory or application pool remain unchanged. Changing it manually works of course, but this would lead to increased support issues.
I have tried changing the upgrade to be a major upgrade, with no success, I am currently working on a custom action to change the .Net version after installation, but I don't have much experience with this feature of Installshield.
Has anyone experienced this issue? Are there any preferred ways of achieving this? (custom actions, or a .Net installer class, WIX is not an option)
Thanks
Without spending hours to dig into it... one quick solution would be to rename the app pools in your new installer and let a major upgrade create the new and remove the old. After all, if you are changing from .NET 2.0 to 4.0, in a sense you are creating a component that is not backwards compatible and thus should be a new component.
Running on Windows Server 2008 R2 with Windows 7 client.
I downloaded and installed VisualSVN Server 2.5.2 without a problem. The page here indicates that this is built against Subversion 1.7.2.
I downloaded and installed TortoiseSVN 1.7.3 without a problem. The page here indicates that this is built against Subversion 1.7.2.
Now I would like to install ankhsvn for use with Visual Studio 2010. The latest version is 2.3.10509 and the page here indicates that this is built against Subversion 1.7.1.
Does anyone know if this will run correctly against my SVN server? Or do I need to wait until ankhsvn release a version built agains SVN 1.7.2? If I need to wait, how promptly do ankhsvn releases usually appear?
Source control is obviously critical so I don't want to risk losing any data by "just trying it".
Subversion versioning requires clients to have the same minor version. So any 1.7.X client should be compitable with every other 1.7.Y client.
For the server, any 1.X client will work with any 1.Y client.
Of course it's a good idea to keep things as up-to-date as possible, but you're not risking anything by combining 1.7.1 and 1.7.2.
The release of AnkhSVN based on 1.7.2 will be out in the coming days, the daily builds are already using this.
From what I'm aware of, we had to upgrade SVN on our servers to be compatible with the latest version of ankhsvn. It was a big deal, for the leads let us know we couldn't use ankh until we updated.
We are also using Tortoise.
Hope that helps.
I recently updated Visual Studio 2010 to SP1 and noticed the .NET 4 framework changed from version "4.0.30319.1" to "4.0.30319.225". I was not able to locate an updated .NET 4 framework installer for "4.0.30319.225". I could only find an update exe which is used to update a particular machine. When I deploy my application now, it still uses the older pre-SP1 version of the framework.
Is there a new bootstrapper that I should be using? Are there any issues with deploying an application that is developed/tested on "4.0.30319.225" to a target machine which only has "4.0.30319.1" ?
According to a comment on Announcing Visual Studio 2010 Service Pack 1 (check page two of the comments) from Jason Zander:
There have been questions about
updates to the .NET Framework. There
is no full service pack for .NET
Framework 4. However there is an
update which you can download from
here: go.microsoft.com/fwlink. The
outline of fixes (linked from the
download page) is here:
support.microsoft.com/.../2468871.
This update is titled "Microsoft .NET
Framework 4 KB2468871". You can read
more about what is in the update on
the download page.
As I mentioned in a previous comment,
VS2010 SP1 requires this update and
will automatically install it as part
of setup.
When you build a project using VS2010
SP1, it does not force a dependency on
the update. Whether you need to
deploy the update with your client or
server application depends on your
need for the fixes in the update. You
will need to look through what it
contains to make that call.
I've personally seen no issue publishing to a server before running the update manually.
I can't speak to the bootstrapper question.