I have only just started playing with Visual Studio .Net having been a "notepad" and "response.write" debug type until now. I have a number of asp based websites and I wanted to try them out in the VS .net debug environment (all on my local w2k system). <BR><BR>The sites work as expected until I set a breakpoint in the code. I have set up VS .net to debug asp rather than asp.net. When I run like this I get an error "unable to open registry key" at the point where the Access database connection is made. Thereafter I can't even run the sites "as normal".<BR><BR>Presumably VS .net is changing some permissions/setups in the virtual directory but it's nothing obvious (to me). Can anyone point me in the right direction please?<BR><BR>Thanks,<BR>JohnOpen up Visual Studio and open up the ASP.NET Web page. Make sure the Web Page contains:<BR><BR><%@ Page Debug="True" %><BR><BR>at the top. Set a break point. Now, Goto Tools/Debug Processes, and Attach the aspnet_ewp.exe process (you will need to check the "Show system processes" checkbox). Now, run the ASP.NET Web page (F5, or via the Build menu).<BR><BR>An instance of IE should open and you should be taken back to VS.NET at the marked breakpoint.<BR><BR>hth, let me know if it works for you... 
Hi Scott,<BR>Thanks for the suggestion but...<BR><BR>I don't seem to have the process you mention on the list (even with "show system processes" ticked.<BR><BR>I did make a little progress from my earlier post by double-checking all the permissions on the directories. Some of them did not have the appropriate security/user settings. After sorting that I now get:<BR><BR>Microsoft OLE DB Provider for ODBC Drivers (0x80004005)<BR>[Microsoft][ODBC Microsoft Access Driver] Cannot open database '(unknown)'. It may not be a database that your application recognizes, or the file may be corrupt.<BR><BR>As I mentioned before, this is (was?) a fully working site but now that I have VS.net'd it, it doesn't even work when I access it outwith VS.net (ie http://localhost).Basically finger trouble and gross stupidity.<BR><BR>The initial problems led me to believe I had a problem with the database drivers, so I downloaded the latest versions from microsoft (which are of course version 2.6). After discovering the permissions problems I "forgot" I still had version 2.6 of mdac installed. When I finally realised and re-installed version 2.7 everything sprang to life.<BR><BR>John
Hi Scott,<BR>Thanks for the suggestion but...<BR><BR>I don't seem to have the process you mention on the list (even with "show system processes" ticked.<BR><BR>I did make a little progress from my earlier post by double-checking all the permissions on the directories. Some of them did not have the appropriate security/user settings. After sorting that I now get:<BR><BR>Microsoft OLE DB Provider for ODBC Drivers (0x80004005)<BR>[Microsoft][ODBC Microsoft Access Driver] Cannot open database '(unknown)'. It may not be a database that your application recognizes, or the file may be corrupt.<BR><BR>As I mentioned before, this is (was?) a fully working site but now that I have VS.net'd it, it doesn't even work when I access it outwith VS.net (ie http://localhost).Basically finger trouble and gross stupidity.<BR><BR>The initial problems led me to believe I had a problem with the database drivers, so I downloaded the latest versions from microsoft (which are of course version 2.6). After discovering the permissions problems I "forgot" I still had version 2.6 of mdac installed. When I finally realised and re-installed version 2.7 everything sprang to life.<BR><BR>John