A .Net AddIn doesn't get autoloading after I moved to Windows7

I creates an addin which runs in XP.
In XP I simply load the .Net dll only once.
The next time I launched MicroStation the dll gets loadung automatically.

I created a form based on BMW and put some commands on it.
If I call 
- ActiveDesignFile.Close() the addin gets unloaded
- OpenDesignFile(...) the addin gets loaded again

Now I moved to Windows7 and the AddIn doesn't get autoloaded anymore.
Are there anybody who has a hint to solve this issue?

code:

[Bentley.MicroStation.AddIn(MdlTaskID ="MyName"]
internal sealed class Connector : Bentley.MicroStation.AddIn, _ApplicationEvents
{
  ...


Parents
  • Application Start-Up

    twegener said:
    The next time I launched MicroStation the DLL gets loaded automatically

    A pure MDL application is loaded in the following circumstances …

    1. Explicitly using keyin MDL LOAD APP_NAME
    2. Automatically, if either
      1. APP_NAME is added to the list of MDL applications specified by MS_DGNAPPS

        or

      2. APP_NAME is added to the list of MDL applications specified by MS_INITAPPS
    3. Automatically, if MicroStation is started with the command-line ustation.exe -waAPP_NAME

    In all cases except 1, the application must be written to behave correctly when loaded as either an MS_DGNAPPS or an MS_INITAPPS.

    Is a .NET AddIn expected to behave differently?

    Regards, Jon Summers
    LA Solutions

     
    Regards, Jon Summers
    LA Solutions

Reply
  • Application Start-Up

    twegener said:
    The next time I launched MicroStation the DLL gets loaded automatically

    A pure MDL application is loaded in the following circumstances …

    1. Explicitly using keyin MDL LOAD APP_NAME
    2. Automatically, if either
      1. APP_NAME is added to the list of MDL applications specified by MS_DGNAPPS

        or

      2. APP_NAME is added to the list of MDL applications specified by MS_INITAPPS
    3. Automatically, if MicroStation is started with the command-line ustation.exe -waAPP_NAME

    In all cases except 1, the application must be written to behave correctly when loaded as either an MS_DGNAPPS or an MS_INITAPPS.

    Is a .NET AddIn expected to behave differently?

    Regards, Jon Summers
    LA Solutions

     
    Regards, Jon Summers
    LA Solutions

Children