References & Version Control

[Joel Palmer]

I have many "helper" projects that I include in a lot of solutions.  When I open a solution and projects exist that have mismatched Telerik references I run the "Telerik-->UI for WPF-->Upgrade Wizard" to bring everything up to the same versions.  I love the tool.  However, I don't like a byproduct.

My scenario is, I have brought the latest Telerik references to projects "helper1" and "helper2" from previous wizard runs in other solutions but the target solutions has "project1" with old references.  I run the wizard and it updates "helper1" and "helper2" along with "project1".  Then, when I check my work into TFS, I see that ALL Telerik controls, not just what is referenced in the projects, are checked into version control.

Can you help me understand why everything must be checked in instead of just what was referenced?
Can you help me understand why the helper projects are upgraded for every solution that they are used?

Thanks for your help,
Joel

[Vesko]

Hello Joel,

Thank you for your feedback.

We choose to include all the assemblies in order to make the entire solution easily portable. To build and configure the project you only need to get the solution from the source control for example. You don't need to have any Telerik product installed.

Regarding your second question - we upgrade all the projects in the solution that is currently loaded by default. However, you can choose which projects to be upgraded in the upgrade wizard. Of course an improvement could be made here if we include a filter and allow only the projects that are not up-to-date to be upgraded or to deselect the projects that are up-to-date.

Please let us know if that answers your questions or you have anything else in mind.


Regards,
Vesko
Telerik

 

 

[Joel Palmer]

I finally figured out what this scenario is:

Add a helper project that references Telerik to Solution 1,

Add the same helper project to Solution 2.

Update the references on Solution 2 using the Telerik WPF Wizard.

Project's hint is pointed to Solution 2's ...\lib\RCWPF... directory.

Open Solution 1 on a machine that does not contain the Telerik Installs. 

View the Helper project's references - in error state.

View the Helper project's hint path - points at Solution 2's ...\lib\RCWPF... directory so update to Solution 1's ...\lib\RCWPF... directory.

[Vesko]

Hi Joel,

Thank you for the feedback.

Please let us know if you  need further assistance.

Regards,
Vesko
Telerik

 

 

[Joel Palmer]

I'm looking for a solution to this scenario... not just to satisfy my own curiosity.

 

Your update utilities are nice.  It seems like a good fit for a solution would be to take the lightweight install of your update utilities (not something heavy like JustCode) and put them on a "new" machine that won't get that a full of Telerik you could handle this scenario.

So, instead of bringing the projects in the solution up to a common version, go through and update the <hint> paths in the project to point to the solutions .../lib... directory.

[Vesko]

Hello Joel,

I think I get what you mean. Until we handle this scenario in the upgrade wizard I suggest you to bring all the solutions that have common Telerik projects on the machine. This should workaround the problem with the broken references.

Regards,
Vesko
Telerik

[Joel Palmer]

Thanks for considering that.  It doesn't seem like that'd be a difficult thing to write and it would show that Telerik continues to be committed to the user's experience... not just to their products. 

[Vesko]

Hi Joel,

Once again we highly appreciate your feedback!

Regards,
Vesko
Telerik