The title of this book is Moving to VB.NET: Strategies, Concepts, and Code. You’ve read about strategies for migrating to VB.NET. You’ve learned the key concepts that every VB.NET developer must know. You’ve seen not only the code changes in the VB.NET language but also sample code intended to teach the concepts behind some of the more important .NET namespaces you will be using.


Configuration File Visual Studio Code Group Runtime Error Dependent Assembly 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    The component was called the ’Animated Button” control—a subset of Desaware’s Custom Control Factory product licensed to Microsoft to be included in Visual Basic. Application B was Visual Basic itself. During their testing process, Microsoft discovered the bug in the control’s Value property and insisted that an error result be returned if a negative value was used. I told them that this would be a serious error due to potential compatibility problems but they insisted that it was a bug and anyone who was setting the property to -1 in their code would just fix their code. Since Microsoft was paying the bills, I changed the code and, sure enough, Application A broke—it was setting the Animated Button’s Value property to -1 in error.Google Scholar
  2. 2.
    No, I have not researched whether these are possible.Google Scholar
  3. 3.
    And no, I did not ask.Google Scholar
  4. 4.
    Remember, this feature does nothing to prevent DLL Hell from occurring with COM components you are using via COM interop.Google Scholar
  5. 5.
    With the exception of the infrequently used, COM-based side-by-side execution described earlier in this chapter.Google Scholar
  6. 6.
    This is a slight simplification. Refer to the online documentation under “How the Runtime Locates Assemblies” for an in-depth description of the loading sequence.Google Scholar
  7. 7.
    This key file was generated specifically for these examples. You should assume that both the public and private key are known publicly and should not use this file for any purpose besides experimenting with these sample programs.Google Scholar
  8. 8.
    If you rebuild a component with the same version number and break compatibility, all bets are off. But you would never do that, right?Google Scholar
  9. 9.
    Here I am extrapolating a bit based on the 1.1 framework as to how future versions are likely to work. This is subject to change.Google Scholar
  10. 10.
    I’m not going to go into further detail of code signing at this point since it will probably be used less frequently than it was with ActiveX controls now that strong names provide the protection from modification that was one of the features of Authenticode.Google Scholar
  11. 11.
    In VS2003, you should copy the configuration file after the executable is built, because the build process deletes existing configuration files. You can also create an app.config file and specify it as an override file in the deployment property page for the project settings. The app.config file will be copied into the build directory for that configuration. The override configuration file must be named app.config.Google Scholar
  12. 12.
    Depending on the OS and Pointer type, trying to write to code will either modify your code or cause a memory exception.Google Scholar
  13. 13.
    This is not entirely accurate for Wmdows 95/98/ME but close enough for our purposes.Google Scholar
  14. 14.
    Role-based security in.NET is actually quite flexible. In addition to allowing identity based on system security accounts and groups, you can define custom roles. You could, for example, create a database of user identities and roles independent of those built into the operating system and use those to base security decisions. Role-based security is, nevertheless, similar in concept to the role-based security with which you are probably familiar. Thus, I will not go into great detail on the subject in this chapter.Google Scholar
  15. 15.
    You can also use the caspol utility program to configure security. In fact, you can even hand edit the system configuration files using a text editor—they are just XML.Google Scholar
  16. 16.
    Individual entries may vary on your system depending on your configuration and whether you are using VS2002 or VS2003.Google Scholar
  17. 17.
    The version numbers, tokens, and message details may differ on your system.Google Scholar

Copyright information

© Daniel Appleman 2003

Authors and Affiliations

  • Dan Appleman

There are no affiliations available

Personalised recommendations