we have been using the automation toolkit for one and a half year, and our *.sln file contains below properties:

GlobalSection(ExtensibilityGlobals) = postSolution
ShellProjectGuid = {90ae59ae-e404-4102-9076-9fe9ca60f47e}
CommonProjectGuid = {9993ae7c-e9ea-4e6a-8374-c8f213bc9721}
RootNamespace = COM.OOCL.TMS
EndGlobalSection

Only with above information we can use the automation toolkit.

But the odd thing is that every time we open the *.sln file, the clear case(our source control tool) add-in in visual stuidio will pop up a dialog window asking us to check out the *.sln file 3 times(same with the properties below GlobalSection(ExtensibilityGlobals).

If I change the postSolution to be preSolution, it won't pop up window asking check out.

This is really unbelievable and bother us for a long time.

Doesthere any body have any idea about this?

Thanks for all your advice.

Hi Ryan,

We haven't seen that behavior with TFS or VSS so as you guessed it's most probably a ClearCase intregration related issue.

I can see those are common settings stored at the solution file either by any of the guidance packages you're using or any other code or Visual Studio itself (this later one may complicate things). Which are the ones you're using? Any from p&p? Or have you custom code your own package from scratch? After knowing this, you may be able to change the location where the settings are stored and avoid the ClearCase issue...

Did you have a chance to contact ClearCase support to learn if this is a well-known issue of their product?

thanks,
-Victor.

Hi Ryan,

Sorry I forgot to check back this thread. Can you please check if Luciano's solution works for you? If not, please let me know (you can reach me at vga AT clariusconsulting DOT net) and I'll loop you with the SCSF's PM.

thanks,

-Victor.

I had ested with VSS and found that it worked fine under VSS.

So I think it's the ClearCase who can't recognize the GlobalSection(ExtensibilityGlobals) tag. May be it's the problem of integration between clear case and visual stuido again. This kind of problem will not be solved anyway as I met before.

Anyway, constructive suggestion will still be welcomed.

Hi Ryan,

We haven't seen that behavior with TFS or VSS so as you guessed it's most probably a ClearCase intregration related issue.

I can see those are common settings stored at the solution file either by any of the guidance packages you're using or any other code or Visual Studio itself (this later one may complicate things). Which are the ones you're using? Any from p&p? Or have you custom code your own package from scratch? After knowing this, you may be able to change the location where the settings are stored and avoid the ClearCase issue...

Did you have a chance to contact ClearCase support to learn if this is a well-known issue of their product?

thanks,
-Victor.

Thanks for your kindly and helpful comments. I have read some artical about using of solution file(*.sln).
And I have focused the questions as below:

1. what is the difference of action preSolution and postSolution when devenv load the solution using solution file.
2. Why clear case have to check out solution file if the devenv.exe read the props of ExtensibilityGlobals in solution file.

The second question I have asked the CC guys.
Hope you can enlighten me about the first question.

Thanks.

Hi Ryan,

I've contacted the SCSF team directly and they will look into this to see if there is any quick workaround they can provide to avoid the CC issue.

I'll keep you posted.

thanks,
-Victor.

I had checked our Gudiance Package source code, and found that we can avoid set the ExtensibilityGlobals in the

*.sln file.We can hard code the needed global values in the source code. I know this is bad, but we can avoid the anoyying check-out issuses anyway.

By the way, I have asked ClearCase guys, but there is no response until now.

I would appeciate if you kept me posted once you got any idea from SCSF team, thanks for your kindly post.

Hi all!

I have taken a look to this, and modified the SCSF Guidance Package in order to store these globals in an xml file. I haven't tried it with ClearCase, but at least with this customized gp it will not have the conflicting globals in the .sln file.

I wrote a post in my blog where I provide the guidance package ready to be registered. You can check it here.

Hope it helps!

Luciano G. Panaro

http://staff.southworks.net/lpanaro

Hi Ryan,

Sorry I forgot to check back this thread. Can you please check if Luciano's solution works for you? If not, please let me know (you can reach me at vga AT clariusconsulting DOT net) and I'll loop you with the SCSF's PM.

thanks,

-Victor.