|
code
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Access Progammer to VB.Netincludee VB.NET instead of MS Access and VBA. Theres no jobs for high level Access developers anymore. Anyway, there are couple of debugging tools I'm use to using in Access that I can't seem to find in Visual Studio.Net. 1. I use the F8 function key to step though code one line at a time in MS Access. I know Visual Studio.NET has a debug button that allows me to do this, but I am wondering if VS.Net would allow me to use the F8 key like I'm used to in Access? 2. Last, in Access I depend very heaviliy on the Debup.Print feature to display output results in the Immediate Window. Or, I can just type in a variable name into the Immediate Window during code execution and see what the value is. How do I get the equivilant Immediate Window and functionality in Visual Studio.NET. Its the only way I really am able to debug my code. 3. Oh, and just one more thing. In Access you can hover over your code during executing and intellesense will display the resulting value. Do I need to activate something in VS.NET for this feature to work? Or, am I just going to have give up these tools and figure out another way? Thanks for your help. Greg Any help on Number 2 would be very helpful.
Show quote
Hide quote
"Greg" <AccessVBAnet@newsgroups.nospam> wrote in message #1: The VS.Net IDE is highly extensible.news:5E6EDB1C-22C0-4A8A-BE82-F5CE707D86DF@microsoft.com... > I've just decided to bite the bullet and upgrade my programming skills to > includee VB.NET instead of MS Access and VBA. Theres no jobs for high level > Access developers anymore. > > Anyway, there are couple of debugging tools I'm use to using in Access that > I can't seem to find in Visual Studio.Net. > > 1. I use the F8 function key to step though code one line at a time in MS > Access. I know Visual Studio.NET has a debug button that allows me to do > this, but I am wondering if VS.Net would allow me to use the F8 key like I'm > used to in Access? > > 2. Last, in Access I depend very heaviliy on the Debup.Print feature to > display output results in the Immediate Window. Or, I can just type in a > variable name into the Immediate Window during code execution and see what > the value is. How do I get the equivilant Immediate Window and functionality > in Visual Studio.NET. Its the only way I really am able to debug my code. > > 3. Oh, and just one more thing. In Access you can hover over your code > during executing and intellesense will display the resulting value. Do I need > to activate something in VS.NET for this feature to work? > > Or, am I just going to have give up these tools and figure out another way? > > Thanks for your help. > > Greg > > Any help on Number 2 would be very helpful. Take a peek at ... Tools::Options::Environment::Keyboard::Keyboard Mapping Scheme. #2: You have to add the 'Debug' class to your code import System.Diagnostics .... Debug.WriteLine(...) ' will print to the Output window. #3: "Hovering" only works in Debug mode. But I might be wrong thus ... You need to post this in a dotNet newsgroup... microsoft.public.dotnet.languages.vb microsoft.public.vsnet.general microsoft.public.vstudio.general -ralph And if you do post to another group, can you perhaps tell us where you're
moving it to...some of us who are Access programmers and may soon be forced into .Net would really appreciate following this thread, wherever it goes. :) RobShow quoteHide quote "Ralph" <nt_consultin***@yahoo.com> wrote in message news:2omdnWJiN_LhonTYnZ2dnUVZ_vKunZ2d@arkansas.net... > > "Greg" <AccessVBAnet@newsgroups.nospam> wrote in message > news:5E6EDB1C-22C0-4A8A-BE82-F5CE707D86DF@microsoft.com... >> I've just decided to bite the bullet and upgrade my programming skills to >> includee VB.NET instead of MS Access and VBA. Theres no jobs for high > level >> Access developers anymore. >> >> Anyway, there are couple of debugging tools I'm use to using in Access > that >> I can't seem to find in Visual Studio.Net. >> >> 1. I use the F8 function key to step though code one line at a time in MS >> Access. I know Visual Studio.NET has a debug button that allows me to do >> this, but I am wondering if VS.Net would allow me to use the F8 key like > I'm >> used to in Access? >> >> 2. Last, in Access I depend very heaviliy on the Debup.Print feature to >> display output results in the Immediate Window. Or, I can just type in a >> variable name into the Immediate Window during code execution and see >> what >> the value is. How do I get the equivilant Immediate Window and > functionality >> in Visual Studio.NET. Its the only way I really am able to debug my code. >> >> 3. Oh, and just one more thing. In Access you can hover over your code >> during executing and intellesense will display the resulting value. Do I > need >> to activate something in VS.NET for this feature to work? >> >> Or, am I just going to have give up these tools and figure out another > way? >> >> Thanks for your help. >> >> Greg >> >> Any help on Number 2 would be very helpful. > > #1: The VS.Net IDE is highly extensible. > Take a peek at ... > Tools::Options::Environment::Keyboard::Keyboard Mapping Scheme. > > #2: You have to add the 'Debug' class to your code > import System.Diagnostics > ... > Debug.WriteLine(...) ' will print to the Output window. > > #3: "Hovering" only works in Debug mode. > > But I might be wrong thus ... > > You need to post this in a dotNet newsgroup... > microsoft.public.dotnet.languages.vb > microsoft.public.vsnet.general > microsoft.public.vstudio.general > > -ralph > > > "Robert Morley" <rmor***@magma.ca.N0.Freak1n.sparn> wrote in message Just to muddly the waters a bit. (In case you haven't heard.) The MS Accessnews:e5xVB0bXHHA.2320@TK2MSFTNGP03.phx.gbl... > And if you do post to another group, can you perhaps tell us where you're > moving it to...some of us who are Access programmers and may soon be forced > into .Net would really appreciate following this thread, wherever it goes. > :) > > > Rob > > > <snipped> group has taken over Jet development and introduced a new enhanced version of DAO (uh..., make that ACEDAO) to go with the new Jet (uh..., make that ACE) along with PIAs for ADO, DAO, and ACEDAO, as well as some sort of rumored "ACE.Net/ADO.Net" thingy. The Access newsgroups are sure to be busy. <g> -ralph Hi Greg,
I think Ralph's reply basically covers all your questions and I agree with him. As he already pointed out, this newsgroup is mostly for asking VB6 related questions, questions related to VB.NET will be best served via newsgroups such as microsoft.public.dotnet.languages.vb (which is also a managed newsgroup). Anyway, please feel free to follow-up here or post in other newsgroups if you need anything else. Thanks. Regards, Walter Wang (waw***@online.microsoft.com, remove 'online.') Microsoft Online Community Support ================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights. 
Other interesting topics
|
|||||||||||||||||||||||
