> Peter, thanks for the reply. I know I have a lot of learning to do in
> moving from VB6 to VB.net. That aside, I opened a .vb file that another
[quoted text clipped - 48 lines]
>> microsoft.public.dotnet.languages.vb (as you're interested in Visual
>> Basic)
>I just noticed something, if I create a new class library solution then it
>adds a bunch of supporting files such as assemblyinfo.vb, .sln etc. With
>this setup intellisense works. But if I just open a .vb file by itself it
>doesnt. The vb file has all the imports statements at the top...
>
> thanks!
OK, you've discovered that VS.NET works on a solution basis, not an
individual file basis.
Same thing with C++ source code files. I *used* to be able to open a C++
source code file in VS 6 and get a project automatically built around it
when I compiled. No more in VS .NET. Must create a project first, then add
the source code file to the project to work with it. Win some lose some, I
guess. I find all the plusses in Visual Studio .NET 2003 greatly outweigh
any minuses, so I adapt and move on.
Have fun!

Signature
Peter [MVP Visual Developer]
Jack of all trades, master of none.
red floyd - 03 Mar 2005 18:28 GMT
>>I just noticed something, if I create a new class library solution then it
>>adds a bunch of supporting files such as assemblyinfo.vb, .sln etc. With
[quoted text clipped - 12 lines]
> any minuses, so I adapt and move on.
> Have fun!
What I'd really love to see is the VS6 IDE with the VC++7.1 compiler
back-ending it.
Michael Viking - 03 Mar 2005 19:12 GMT
<SNIP>
> What I'd really love to see is the VS6 IDE with the VC++7.1 compiler
> back-ending it.
No question! Add in some bug fixes and this would be something I'd pay good
money for.
-Michael Viking
param@community.nospam - 04 Mar 2005 16:56 GMT
Ok agreed I have a lot of learning to do as far as how vs.net works. But in
my situation I already have a bunch of code developed by another developer
using notepad and the sdk compilers. I am just trying to find the best way
to continue where he left of by opening his files (mostly aspx pages with
.vb dlls in bin folders) in vs.net and make use of some of the features of
vs.net like intellisense, compiling without having to launch command line
compilers etc.
thanks!
>>I just noticed something, if I create a new class library solution then it
>>adds a bunch of supporting files such as assemblyinfo.vb, .sln etc. With
[quoted text clipped - 12 lines]
> any minuses, so I adapt and move on.
> Have fun!
Peter van der Goes - 04 Mar 2005 18:51 GMT
> Ok agreed I have a lot of learning to do as far as how vs.net works. But
> in my situation I already have a bunch of code developed by another
[quoted text clipped - 5 lines]
>
> thanks!
From what you've said about the files left to you. it sounds like the other
developer was creating web applications using VB.NET and ASP.NET.
In Visual Studio terms, that would be Project Type = Visual Basic Projects,
Template = ASP.NET Web Application.
In your shoes, I'd be tempted to try creating a VB Web application, then try
substituting the files you have for the files created by the application
wizard. I hope the other developer left a little documentation and organized
the files into project groups for you?

Signature
Peter [MVP Visual Developer]
Jack of all trades, master of none.
param@community.nospam - 05 Mar 2005 17:10 GMT
Correct VB.Net & Asp.Net. The only thing he didnt use VS.Net. No
documentation unfortunately, but he did organize the files by website. So I
have a main folder c:\website files on the IIS server and within that 1
folder for each website.
I have tried File-->New-->VB Projects-->Asp.Net Web Application, but
apparently that wizard has some frills to it e.g. it tries to connect to the
iis server, create vdirs, .config files and permissions etc. Granted all
these are cool for a newbie and maybe even good for starting a new project,
but in my case I just want to open the files already there without jumping
through too many hoops! lol! I may try your idea of creating a new web app
and then moving the other files over, but that would mean I would have to
setup new vdirs & websites under IIS instead of using the ones already
there. Oh well I will give it a shot
Thanks!
>> Ok agreed I have a lot of learning to do as far as how vs.net works. But
>> in my situation I already have a bunch of code developed by another
[quoted text clipped - 14 lines]
> application wizard. I hope the other developer left a little documentation
> and organized the files into project groups for you?