Friday, August 12, 2005 12:42 AMHere's what I want to do:
I have a parser generator that I want to use in my project, and
what I want is to be able to edit the grammar file and have a
custom tool generate the code for me automatically (similar
to web references and the MSDiscoCodeGenerator).
Could anyone point me to how to some document that explains
how to do this in VS2005:
* Which tools/sdk's do I need?
* How do I create the new file type in VS2005? (do I have to?)
* How do I create the custom tool for VS2005?
I've seen some articles on how to do this stuff for VS2003, but
I am not sure I should do the same for VS2005.
Thanks in advance,
Friday, August 12, 2005 2:00 AMIf you're using VB/C#/J#, you might want to look into single-file generators:
Friday, August 12, 2005 2:48 AMThe document you pointed out has a link to an implementation
of BaseCodeGeneratorWithSite in gotdotnet, however it indicates
that it works for VS 2002 and 2003, not for 2005.
My question is - is this still the "preferred" way to do what I
want in VS2005, or is there a new supported/preferred method?
And finally, after reading that, I've got another question:
Does this method work if I need a custom tool that generates
more than 1 file from 1 input file?
Monday, October 10, 2005 11:41 PMIVsSingleFileGenerator is still the method for 1 in:1 out.
1 in:multiple out isnt a tool, you handle that thru the build system.
Sunday, October 16, 2005 4:31 PMI have the same issue - I have the "Visual Studio 2005 Team System Extensibility Kit Beta 2" installed. I can see the following assemblies when I browse to C:\Windows\assembly
However, when I try to reference these assemblies from the GAC tab in VS 2005, they are no where to be found. I also see several other assemblies missing from this tab that I can see in C:\Windows\assebly - such as many of the Microsoft.TeamFoundation.* assemblies.
I'm guessing there some version mismatch barrier, but is there any diffinite instuction on how to do this? I have hundreds of Custom Tools I've written for VS.NET 2003 that I'd like to VS2005, but Custom Tools (Single File Generators) seems to be missing from your VS Extensibility story thus far.
When you see reference the assemblies from the SDK install, what exactly do you mean? I'm assuming by "SDK", you're referring to the Extensibility Kit, and what location is that? I don't see any install directory for that.
Please advise - perhaps the solution is to wait for the Beta 3 Extensibility Kit?
Thanks in advance.
Monday, October 17, 2005 7:11 PMno, when I say SDK I mean the VS SDK.
The Team System Extensibility Kit is a different beast. Future versions of the TFS EK will ship as part of the VS SDK.
Monday, October 17, 2005 8:12 PMThanks for the reply
ok, any thoughts on why the assemblies aren't showing up in the the References tab?