|
|
|
Forum Member
 
Group: Forum Members
Last Login: 2/15/2007 10:36:50 PM
Posts: 25,
Visits: 25
|
|
| I've noticed that the server control accepts connection at design-time. This behavior should be modified so that it does not actually run at design-time. Also, it may be a good idea to set the AcceptConnections property to False by default. Lastly, when I set the property to False on the design form it sets itself back to True after closing and re-opening the form. This is a bit annoying.
|
|
|
|
|
Supreme Being
Group: Administrators
Last Login: Yesterday @ 7:10:09 PM
Posts: 1,163,
Visits: 1,909
|
|
Thanks for the bug report! Yes the behaviour you are describing is a known bug. Basically the bug is that the ActiveX doesn't detect "Design-time state". This will be fixed of course.
In the current beta this design-time unawares causes one small problem. Currently the ActiveX uses a mutex, to prevent several ActiveXes to run at once. If you instantiate a second copy of ServerX the control will refuse to create.
This causes the following problem. If you have a Windows Form or ASP.NET page with ServerX on it open in Visual Studio, and you start debugging your application, the control won't be instantiate for the debugging application since there is an instance of the ActiveX in VS designer. To workaround this problem you should close Windows Form/ASP.NET page in VS before started your application.
Kindest Regards,
SmartCode Solutions Support
|
|
|
|
|
Supreme Being
Group: Administrators
Last Login: Yesterday @ 7:10:09 PM
Posts: 1,163,
Visits: 1,909
|
|
|
|
|