TFS - Rolling back to a previous release / CRM 2011

Hi,

Is the deployed solution a "Managed" solution? If yes, you can remove that solution. And it should do the revert.

No, this is a development environment, the solutions are all unmanaged

Thanks

Yes, so to get back to the last good release, I am rolling back to the last tested package.

Once that is done, it should be able to be tested by the client and promoted to Production.

However, since I had to roll back to the end of February, there have been three builds in March.

How do I get the individual solutions out the March packages to add to a new clean version?

Well, you will not be able to rollback. The components has to be removed manually or whatever modifications done after Feb should be modified/removed manually to get to its original state.

We use TFS to run Solution Packager and some custom software that gives an incremented package and also increments the CRM solution version.  So far it is testing OK at each server level

Here is what I did

1.      Right-click on the folder in Source Control Explorer. Choose Get Specific Version. Choose the version that you want to get (by changeset, date, label, etc).
2.      EDIT: At this point your local version will be the version that you want.
3.      Check out the changed files and then check them back in.
4.      This will bring up the merge wizard and it will probably be complaining about how the server has a newer version than you do.
5.      Go through the wizard and merge the files the way you want them (one of the options is to discard the server changes, which is what it sounds like you want).
6.      At the end of this process, it may tell you that no files were checked in due to the merge process (or something of that nature), just hit OK and then check in again. This should accomplish what you need.

I am stuck at the pre-prod server, while the package is publishing customizations, I get the following error:

Unhandled Exception: System.TimeoutException: The request channel timed out while waiting for a reply after 00:40:00. Increase the time
out value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have
been a portion of a longer timeout. 

Select allOpen in new window

Any idea on how to increase the time-out?  It works on the dev and test but gives me this error on pre-prod

Thanks

This suggestion was what we ended up doing.  There is no way remove an unmanaged solution so this just wrote over it.

Thanks