 |
Submit Your Code | |
 |
SEO Monitor | |
 |
UpTime Monitor | |
 |
PHP Code Contest | |
 |
My Favorite Examples | |
|
My Favorite Articles | |
 |
Update Your Profile | |
|
|
| More Weber Sites | ||
| PHP Code Search | ||
| Web Development Forums | ||
| Learn MySQL Playing Trivia | ||
| PHPBB2 Templates | ||
| Web Development Index | ||
| PHP Web Logs (BLogs) | ||
| Web Development Resources | ||
| Web Development Content | ||
| Recommended Links | ||
| PHPClasses | ||
| PHP Editor | ||
| PHP Jobs | ||
| Vision.To Design | ||
| Ajax Tutorials | ||
| PHP Programming Help | ||
| PHP/MySQL Programming | ||
| Webmaster Resources | ||
| Webmaster Forum | ||
| XML meta language | ||
| website builder | ||
| Recommended | ||
| Submit Site | ||
| Forex Trading Online forex trading platform | ||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Code | |||||
The information in this article applies to: - Microsoft Visual InterDev, version 6.0 SUMMARY ======= This Knowledge Base article will briefly describe the steps involved to set up remote debugging for use with Visual InterDev Version 6.0. NOTE: It is required to have the server components installed on the server for remote debugging to work. MORE INFORMATION ================ Configure NT Permissions for Users That Need to Remote Debug ------------------------------------------------------------ In order to correctly use remote debugging you must be part of the administrators group on the Internet Information Server (IIS) server machine. NOTE: Microsoft understands that this is a limitation and any new information regarding this issue will be posted in the Knowledge Base. Using the User Manager for Domains, add the Windows NT user account that will be used for remote debugging to the administrators group. Only one account can be used for remote debugging at a time. Granting permissions to a group such as the Administrators group is not recomended. Configure DCOM Permissions -------------------------- 1. From the Start button, click Run on the server computer. 2. Type "dcomcnfg.exe" and click OK. 3. On the Applications tab, scroll down to the Catalog Class and select it (single click). NOTE: The Catalog Class item is installed with Back Office Installation Wizard and is part of the Server components for Visual InterDev 6.0 4. Click the Properties button to display the Properties dialog box. 5. Click the Security tab. 6. Select "Use custom access permissions" and click Edit. Add a user who is part of the administrators group on that machine. Grant the user "Allow Access" rights. 7. Select "Use custom launch permissions" and click Edit. Add the same user here and grant them "Allow Launch" rights. 8. Select "Use custom configuration permissions" and click Edit. Add the same user here as well and grant them "Full Control." 9. Select the "Identity" tab. 10. Select the "This user" option for the user account you want to run for this application. 11. Type in the domain and userid of the user who you added in the above steps. 12. Type that user's password both in the "Password" and "Confirm Password" boxes. 13. Click OK to exit the Catalog Class Properties dialog box. 14. Display the Properties dialog box for the "Machine Debug Manager" item. Repeat steps 4-13 for the Machine Debug Manager. 15. Select the "Default Properties" tab on the Distributed COM Configuration Properties dialog box. 16. Ensure that the check box for "Enable Distributed COM on this server" is selected. 17. Set the "Default Authentication Level" to "Connect." 18. Set the "Default Impersonation Level" to "Identify." Configure your Application for Remote Debugging ----------------------------------------------- 1. Open the Internet Service Manager (ISM) in the Microsoft Management Console (MMC). 2. Display the properties dialog box of the application you wish to remote debug. (Right-click and select properties) 3. On the "Directory" tab select the "Run in separate memory space" check box. 4. Click the Configuration button. NOTE: The directory must be marked as an Application Root designated by a blue package icon. 5. Select the APP Debugging tab. 6. Check the "Enable ASP Server-Side Script Debugging" check box. 7. Check the "Enable ASP Client-Side Script Debugging" check box. 8. Click OK to close the Configuration dialog box. 9. Click OK to close the Properties dialog box. Configure Microsoft Transaction Server for Remote Debugging ----------------------------------------------------------- 1. Open the Microsoft Transaction Server Explorer in the MMC. 2. Under "Microsoft Transaction Sever, Computers, My Computer, Packages Installed" select the package for your Web application. 3. Display the Properties dialog box for your Web application (right-click and select Properties). 4. On the Identity tab, select "This user" and enter the account that you will use for remote debugging and the password. 5. Click the "Security" tab. 6. "Authentication Level for Calls" should be set for anything but "none"; I use "Packet." NOTES: - The next time you open the Properties for this Web application package, the password text spaces will be blank. This is normal, the password is still being stored, and you do not need to re-enter it. - When an account connects from Visual InterDev to debug, it will replace the account information in this dialog box with the debuggers account information. - Since the account will likely not be the same as the debugging account (or could be), the key to this step is selecting the "This user" option button. Entering a valid account ensures that the package can be run by MTS for normal operation when not debugging. The interactive user will not work. - If the debugger fails to attach correctly to the process, several things may happen or need to be done: a. The process will be shut down. b. The application will be changed so that the "run in separate memory space" check box is cleared. c. When the Web application's "isolated process" status changes, the MTS package is destroyed. This will remove the changes made to the package's "identity" tab. The Web application will need the "Run in a separate memory space (isolated process)" check box re-selected (which will create a new MTS package), and the "identity" for that package will have to be reset with a valid "This user" account and password. d. It is recommended that you shut down and restart Visual InterDev before trying another debugging session. How to Manually Set Up a Visual InterDev 6.0 Project for Remote Debugging ---------------------------------------------------------------- 1. Create a new Web project in Visual InterDev 6.0. 2. Add an Active Server Pages (ASP) page to the project. 3. Add the following lines of code to the new ASP page within the HTML body: <% DIM temp temp = "Hello World" Response.Write(temp) %> 4. Click in the border area to the left of the second line (temp = "Hello World"), this will set a breakpoint for that line. A large dot will appear next to the line in the border. 5. Right-click the ASP file name in the Project Explorer and select the "Set As Start Page" option. 6. Right-click the ASP file name in the Project Explorer again, and select "View in browser." Leave your browser running. 7. Select the Processes option under the Debug menu. 8. Type in the name of your IIS machine for which your application is running on and press enter. Alternatively, you may simply click the Machine button and select your IIS machine from the list provided. After a few moments (depending on how many processes are running on your server) the listbox below will be populated with the processes running on your machine. 9. Highlight the Mtx.exe (Microsoft Transaction Server) process by single- clicking it. 10. Click the Attach button. This will attach your remote computer to the ASP application processes running under Mtx.exe and put Visual InterDev into Debug mode. 11. Close the processes dialog box. 12. Refresh your Web page in the open browser. This will invoke the Visual InterDev script debugger. The debugger will break on your breakpoint, and the line will be highlighted. NOTES: - The first time you should see a dialog box asking you if you would like to automatically set the application into debug state. Click Yes and continue. - You should get a dialog box asking you to log on. Log on as the account that you have granted access to for Remote Debugging in the earlier steps. - You should then see the debugger load in the Visual InterDev environment. Shortly after you will see your browser open and begin to load the page. This may take several minutes. When the code hits the breakpoint, the Visual InterDev debugger will again have focus and your line with the breakpoint should be highlighted in yellow. You are now debugging. REFERENCES ========== For more information, please see the "Microsoft Visual InterDev 6.0 Debugging" white paper on the Microsoft Developer Network (MSDN) Online: http://msdn.microsoft.com/developer/news/feature/visep98/videbug.htm | |||||
| Related Code Examples | |||||
