Global VBProjectAssembly

Hi Alex,

When you create a new VBSyntaxLanguage, you normally are setting a VBProjectAssembly to it.  You have two choices:

1) You could create a single instance of the VBProjectAssembly.  Then store it statically in your app and apply that to every VBSyntaxLanguage you create.

or

2) You could create a single instance of a VBSyntaxLanguage and store it statically in your app.  Make a single instance of a VBProjectAssembly and apply that to the language.  Then whenever you create an editor instance, use that same singleton language instance.  Languages are intended to be reused across multiple editors/documents.

As for types not showing, that all depends on which assemblies you have referenced from your VBProjectAssembly and which namespaces have been imported.  For instance, if you forgot to reference things like MsCorLib, types such as System.Int32 might not show up in IntelliPrompt, even if you import the System namespace.  Think of project assemblies like a Visual Studio project.  IntelliPrompt will show whatever types are available based on the referenced assemblies (set on the project assembly) and imported namespaces (set in the document text).

Hi,

Thank you for the reply.

But the scenario you propose is exactly the one I use and described above, which unfortunately does not work as expected.

About adding the correct references, I can assure you that I reference MsCorLib right from the begining.

Please try to reproduce the issue by following the scenario I wrote.

The product version I use is 12.2.571.0

Hi Alex,

We can take a look but please put together a new simple sample project that just shows this issue and email it to our support address.  Reference this thread, include instructions for the steps to repro it, and be sure to rename the .zip file extension so it doesn't get spam blocked.  Then we can debug your scenario and see what is happening.  Thanks!