Dave,
>We (American Motor Carrier Services)are on Ver 1.1 Should I be upgrading?
>What is the upgrade policy. Actually I was an employee of the Company but the owner(s) retired and I bought it as a result some administrative tasks have slipped through the cracks. Do I need a new maintainace agreement? If so what's it going to cost me?
I'll check into this and send you a private e-mail with the information you need.
>Code generation for property 'SecurityManager' failed. Error was: 'Object reference not set to an instance of an object.
This is a bogus VS .NET error you can ignore. We worked around that in newer versions of MM .NET, so when you upgrade, that error should go away.
>And lastly are there any MM issues if I begin using Asp.net 2.0? I doubt this a good idea yet but I do like the idea of executing out-of-band calls backs without all the trouble of implementing the XmlHttp COM object and JavaScript.
You can give it a try, but I can't guarantee anything (although it should work just fine).
Regards,
Kevin McNeish
Eight-Time .NET MVP
VFP and iOS Author, Speaker & Trainer
Oak Leaf Enterprises, Inc.
Chief Architect, MM Framework
http://www.oakleafsd.com