re: Why C# and VB are not supported for VS Shell Isolated stubs

Victor Garcia Aprea — Fri, 21 Sep 2007 01:16:20 GMT

I do have a different view on the C++ vs. C# vs. VB code for the stub...

Do you really expect people to modify the generated stub code at all? (no matter if it's C++, C# or VB code).

What about proving a configurable stub in .exe form and just use that?

thanks,

-VGA.

re: Why C# and VB are not supported for VS Shell Isolated stubs

CraigSkibo — Fri, 21 Sep 2007 01:27:45 GMT

No, there is no real need for a special Exe that you compile other than:

1) The name that is passed when calling Setup/Start/Remove. That name needs to be unique to your application and not conflict with another app. So if we had a seperate way of defining that app name, such as looking for an .ini file containing the app name and named the same as the exe but with an ini extension, then that would work fine.

2) The resource information embedded within the exe. You should be putting your organization name inside the exe in the file version resources. If a user were to view the file version information, having Microsoft in there would be misleading, and a generic name would not point the user to the author.

Those are the only two items I can think of at this time.