VS SDK and TeamSystem source control problem

Question

Hi,

After installing Visual Studio SDK, C# project  files in my solution are taken in checkout if a build the solution.

I'm the only member of our team that have the SDK installed.

I look at what is added to project file when I build a solution with the SDK installed.

The following XML is added to the prj file:

>   <ItemGroup>
>     <Service Include="{B4F97281-0DBD-4835-9ED8-7DFB966E87FF}" />
>   </ItemGroup>

Is there a way to avoid this modification to prj file ?

Thanks

 

 

 

 

Answer 1

I'm seeing the same thing. I didn't think I installed the SDK but it looks like I did. Hopefully someone will respond either with a solution or work around.

Answer 2

With a bit of searching this looks to be due to the domain specific language tool aka DSL Tools. Unfortunately I haven't figured out a way to turn that off.

Answer 3

There's a text templating option under the options dialog. I set the value to true. That created an error and Dev Studio crashed. But after restarting I don't get the Service element added. There is one thing to realize this seems to foul up the text templating configuration. As I now can't set it back to false.

Answer 4

The insertion of the <Service> tag appears to be a bug in the DSL toolkit. I've opened a bug in our database to track the issue and we'll get it fixed in a future release of the SDK.

Thanks,
Aaron

Answer 5

Hi Aaron,

Is there a work around that can  make us wait for the bug fix?

Thanks

 

 

Answer 6

This <service> tag

 <Service Include="{B4F97281-0DBD-4835-9ED8-7DFB966E87FF}" />

gets (repeatedly) added to the project file when the Text Templating technology that is part of the DSL Tools is in memory inside Visual Studio.

If its never brought into memory then it shouldn't cause a problem.

Loading the DSL Tools brings it into memory, so obviously avoid that if you're not using it.
The presece of the <service> tag itself also brings the text templating service into memory and perpetuates itself.

So as a workaround, if you close VS - delete all instances of the service tag with the guid specified above from your project file and the reopen the project in a clean VS, it should be gone and stay gone.

 

 

Answer 7

FYI...This bug has been fixed in the (upcoming) December 2006 CTP release of the Visual Studio 2005 SDK.

Thanks,

Aaron

Answer 8

The bug with <Service Include="{B4F97281-0DBD-4835-9ED8-7DFB966E87FF}" /> seems still there in December 2006 CTP release of the Visual Studio 2005 SDK. The bug appears after some manipulation with Tools/Options dialog whithout Text Templating options change. See thread at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=954064&SiteID=1.

Answer 9

Thanks Alexey,

I've opened a new bug for us to investigate this.

 

Aaron

Answer 10

Any progress?  I'm still seeing this problem with Orcas Beta 2.

Answer 11

 

We believe we've finally fixed this one for Orcas RTM

 

We no longer mark solution files at all, and we now only mark individual project files when you actually run the T4 custom tool in that project.

Answer 12

This bug is happening to me and I haven't even installed the DSL tools.  I'm still using VS2005 with the december updates so this fix in orcas really doesn't help me.  I've taken all the steps suggested in this thread and it is still continually happening.  This is making it nearly impossible for me to even perform my job.  I can't check in code without building first, and every time I build this happens.  I can't review anyone's code, because if I unshelve it, this becomes part of the change.  This bug needs to be fixed in VS2005...not just orcas

 

Answer 13

I have found that if you just check in the modified project file, including the Service tag, there is no harm caused to other developers who open the project files without having the SDK.  I have also seen no build issues using TFS and MSBuild.  As a workaround, I suggest trying a checkin of a modified project file to see if it will work for you.

 

Answer 14

I didn't have this problem with the Feb 2007 SDK.

 

But.... after i installed the 3.5 sp1 beta 1 the problem seems to be there at least in vs2005. After uninstalling the 3.5 sp1 beta 1 the problem is gone again.