VS SDK and TeamSystem source control problem

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

[573 byte] By [Lakusha] at [2007-12-25]

«« vb and sql express, data from table wihout a control
»» How to start new instance of IE6 from .NET Web Application

# 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.

dbradley at 2007-10-8 >

top of Msdn Tech,Visual Studio,Visual Studio Extensibility...

# 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.

dbradley at 2007-10-8 >

# 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.

dbradley at 2007-10-8 >

# 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

AaronMarten-MSFT at 2007-10-8 >

# 5

Hi Aaron,

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

Thanks

Lakusha at 2007-10-8 >

# 6

This <service> tag

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.

GarethJ-MSFT at 2007-10-8 >

# 7

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

Thanks,

Aaron

AaronMarten-MSFT at 2007-10-8 >

# 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.

AlexeyGapotchenko at 2007-10-8 >

# 9

Thanks Alexey,

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

Aaron

AaronMarten-MSFT at 2007-10-8 >

# 10

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

JamesManning-MSFT at 2007-10-8 >

# 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.