T
Tom Dacon
I just opened VS2005 beta 2 for the very first time and started out with a
good old Hello World windows forms application.
As was my custom in VS2002/2003, I added a call at the bottom of
InitializeComponent() to call my own initialization routine which I placed
over in Form1.vb, finding the InitializeComponent() routine over in the new
Form1.Designer.vb file. Hit F5 and it ran just fine, ended it and brought up
Form1 in design view and pulled an error in the designer (actually a
warning): "Method System.Windows.Forms.Form.p_Initialize' not found. Around
then I noticed the comment above InitializeComponent: ' Do not modify it
in the code editor'
OK. In VS2002/2003, this was the place to put the first-time initialization
call. Where does it goes nowadays, if not there? And what's the deal with
the warning message?
By the way, setting up a virtual machine in Virtual PC to install this on is
THE hot ticket! Try it if you haven't looked at it yet.
Thanks,
Tom Dacon
Dacon Software Consulting
good old Hello World windows forms application.
As was my custom in VS2002/2003, I added a call at the bottom of
InitializeComponent() to call my own initialization routine which I placed
over in Form1.vb, finding the InitializeComponent() routine over in the new
Form1.Designer.vb file. Hit F5 and it ran just fine, ended it and brought up
Form1 in design view and pulled an error in the designer (actually a
warning): "Method System.Windows.Forms.Form.p_Initialize' not found. Around
then I noticed the comment above InitializeComponent: ' Do not modify it
in the code editor'
OK. In VS2002/2003, this was the place to put the first-time initialization
call. Where does it goes nowadays, if not there? And what's the deal with
the warning message?
By the way, setting up a virtual machine in Virtual PC to install this on is
THE hot ticket! Try it if you haven't looked at it yet.
Thanks,
Tom Dacon
Dacon Software Consulting