The document link to has about 1 paragraph on VSWebSite. Is this the total extent of the documentation When will the VSWebSite namespace be fully documented by MS
By the way, this change has broken alot of our code for our commercial product. You would hope for the following:
1) You maintain backwards compatibility with extensibility.
2) If you violate #1, then you document how to port from the old API to the new API.
3) If you violate #2, then you fully document the new API.
Have you tried asking this fine question in the enterprise forum (two down from our the extensibility forum) We don't have any information on VSWebSite because that's not one of the namespaces that we built. I suspect this will be a totally unacceptable answer, but I'd rather send you to the team that owns that question that to hazard a guess myself, or worse yet, have you lurking around here waiting for an answer we don't have.
I suspect Roger was referring to VSWebSite as either class or namespace in one of the IDE assemblies. On my Beta 2 installation it's called VsWebSite.Interop.dll and located in ogram Files>\Microsoft Visual Studio 8\Common7\IDE\PublicAssemblies\ folder.
VSWebSite in VS 2005?
Justin5
The document link to has about 1 paragraph on VSWebSite. Is this the total extent of the documentation When will the VSWebSite namespace be fully documented by MS
By the way, this change has broken alot of our code for our commercial product. You would hope for the following:
1) You maintain backwards compatibility with extensibility.
2) If you violate #1, then you document how to port from the old API to the new API.
3) If you violate #2, then you fully document the new API.
MS has violated all 3!
andplo
Peace brother.
Origamime
Jim,
I suspect Roger was referring to VSWebSite as either class or namespace in one of the IDE assemblies. On my Beta 2 installation it's called VsWebSite.Interop.dll and located in ogram Files>\Microsoft Visual Studio 8\Common7\IDE\PublicAssemblies\ folder.
Thought I'd point it out.
tbohon
Lauriew