Using VS.NET for legacy development?

  • Thread starter Thread starter Vulgrin
  • Start date Start date
V

Vulgrin

At my company, we have some old and some new code bases to our
platform. The majority of our "old" platform is VB COM and traditional
ASP. Our new platform is C# and ASP.NET. We'd really like to
consolidate our development to a single tool, rather than bouncing
between Interdev and VB 6.

Obviously, we can develop the ASP code in VS.NET and replace Interdev
easy enough. However, I cannot seem to in any way attach VS.NET to the
ASP process for debugging. Has anyone else done this successfully?

After doing some initial research, there doesn't appear to be any real
way to use VS.NET to develop / manage the VB projects, but I was hoping
maybe someone else has tackled this already, or that maybe there is a
third party add-on out there I haven't found yet.

Yes, yes, I know its 2005 and that this stuff is very old. But its an
active, heavily used and complicated platform that is being ported in
tiny bits, and maintenence in several different toolsets is painful.
 
Realistically, you are in two worlds. Visual Studio .NET CAN help you develop
ASP, but does not debug it (as you have found). You also cannot create VB COM
components in VS.NET. By the same token, MSDN library comes in two flavors:
VS and VS.NET. It is an unfortunate artifact of moving from one world to
another.

---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************
 
However, I cannot seem to in any way attach VS.NET to the
ASP process for debugging. Has anyone else done this successfully?

not that I know of
After doing some initial research, there doesn't appear to be any real
way to use VS.NET to develop / manage the VB projects

Just to confirm what you've found... there isn't.

Good Luck

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
 
Back
Top