Uff! sure that you and 'time spent in May, June, July ... almost August. Sure and it 's been a while since my first and last post, have been months of hell not only for the heat but also the many problems that I had to put up and I had to solve relentlessly at the cost of work at night: (. ..
After the long period of stress, I want to start over with a very simple post, but I think useful useful: D (at least I have learned a bell'aiuto customization in OWA), I speak of the client script debugging using Visual Studio 2005.
As I said a few more lines' on a few weeks ago I had the need to change the behavior of OWA to integrate with a business intelligence application, and to verify proper operation, and especially the point where my code inept javascript, I used VS 2005 to understand the flow of the JS code for OWA. But let's get to the point, and 'possible to enable' client-side script debugging with VS by a few simple steps:
After the long period of stress, I want to start over with a very simple post, but I think useful useful: D (at least I have learned a bell'aiuto customization in OWA), I speak of the client script debugging using Visual Studio 2005.
As I said a few more lines' on a few weeks ago I had the need to change the behavior of OWA to integrate with a business intelligence application, and to verify proper operation, and especially the point where my code inept javascript, I used VS 2005 to understand the flow of the JS code for OWA. But let's get to the point, and 'possible to enable' client-side script debugging with VS by a few simple steps:
- Enable Script Debugging
- Select the menu item '"Script Explorer" (Ctrl + Alt + N) from the menu' Debug / Wiondows
- IEXPLORE.EXE Select the job from the dialog in the process of aggacio
- Finish the game and 'done! have fun (or good job:) depends on the spirit with which we deal with the debug : D)
