I am converting a small VB.NET 2003 application over to VS 2005. I ran
it thru the 'upgrade' wizard which prompty upgraded it without any real
issues (except some warnings). However, I did notice that it didn't
really take advantage of the new 'My Project' system folder and
namespace - i.e. the AssemblyInfo.vb was still in the main app, along
with app.config, etc etc.
In order to take advantage of the My Project (i.e. My namespace)
properties, I kinda 'hacked' the result as follows:
.. Brought up My Project and then selected the Resources and Settings
tabs - which told me I didn't have a file and would I like to create
it. Said Yes.
.. I then went into the folder itself (via Explorer) and moved
AssemblyInfo.vb into the My Project folder. Then in VS 2005 I selected
Show all files and selected the AssemblyInfo.vb in My Project to
include it in the project.
.. I created a blank VB.NET 2005 project, selected Show All Files, and
saw that also there were two additional files in My Projects -
Application.myapp and Application.Designer.vb. I saw these have to do
with the My namespace, and also the XML for the Application portion of
My Project. So I then copied these two files from this 'blank' project
into my upgraded projects 'My Project' folder and then selected these
files to include.
This seems to have worked, now my 'My Project' looks and works just
like a newly created VB.NET 2005 project. My question is: Is this the
proper approach for creating a fully equipped 'My Project' area with an
upgraded app? Or am I doing WAY too much work, and is there an easier
way to get an upgraded app to work fully with the My Project namespace?
Thanks.
Tom
--