.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
Easy Web
Imran Ghani
Post New Web Links

Active Scripting APIs: Add Powerful Custom Debugging to Your Script-Hosting App

Posted By:      Posted Date: August 21, 2010    Points: 0   Category :ASP.Net
 

Active Scripting is a powerful tool for adding advanced features such as macro capabilities to custom applications. This creates a need for integrated debugging services for new features added with scripting. To address this need, Microsoft has provided a set of COM interfaces for developing debugging services from within the Active Scripting framework. This article illustrates how to use the debugging services published within the Active Scripting framework to create a full-featured script debugger that can provide a multitude of debugging actions including setting breakpoints, call stack viewing, variable browsing, immediate-window viewing, thread enumeration, and application enumeration.

Mike Pellegrino

MSDN Magazine December 2000




View Complete Post


More Related Resource Links

CLR Inside Out: CLR Hosting APIs

  

By using the CLR 2.0 hosting APIs, developers of native hosts can execute managed code in-process with complete knowledge and control over how the CLR behavior can affect their application.

Alessandro Catorcini and Piotr Puszkiewicz

MSDN Magazine August 2006


Cutting Edge: Custom Script Callbacks in ASP.NET

  

ASP. NET client callbacks represent a neat and elegant way to execute server-side code without posting and refreshing the current page. I discussed ASP. NET callbacks in the August and December 2004 installments of Cutting Edge, considering them from the perspective of rendered pages making background callbacks to the server, sending input data to the relevant page, and receiving a response.

Dino Esposito

MSDN Magazine January 2005


Windows Server 2003: Discover Improved System Info, New Kernel, Debugging, Security, and UI APIs

  

There's a lot to say about Windows Server 2003. First of all, it's the first operating system with built-in .NET Framework support, and it's the first 64-bit OS from Microsoft. But wait, there's more! There are lots of new features and APIs in this version as well. For instance, Windows Server 2003 features Hot Add Memory and a number of other arcane new tidbits. There are new APIs for handling threads, directories, and files, and new features like the low fragmentation heap for managing memory and system information. There's vectored exception handling and new UI APIs as well.OS internals expert Matt Pietrek takes a look at the additions he finds most interesting and useful so you'll have a good place to start when you dive into Windows Server 2003.

Matt Pietrek

MSDN Magazine June 2003


Windows XP: Escape from DLL Hell with Custom Debugging and Instrumentation Tools and Utilities, Part

  

Building on his article published in the June issue, which demonstrated several ways to get process and DLL-related information from APIs such as PSAPI, NTDLL, and TOOLHELP32, the author presents some unusual ways to get system-oriented info that you can easily integrate in your own toolkit. There are three tools included as samples: LoadLibrarySpy, which monitors an application and detects which DLLs are really loaded; WindowDump, which retrieves the content and a detailed description of any window; and FileUsage, which redirects console-mode applications to tell you which process is using any opened file.

Christophe Nasarre

MSDN Magazine August 2002


Windows XP: Escape from DLL Hell with Custom Debugging and Instrumentation Tools and Utilities

  

DLL conflict problems can be tough to solve, but a large number of tools are available to help. There are also many Windows APIs that you can use to build custom debugging tools. Three such tools are discussed here and provided as samples. DllSpy lists all the DLLs loaded in the system and the processes that are using them. ProcessSpy enumerates the running processes and exposes the DLLs they are using, and ProcessXP displays the list of concurrent running sessions for Windows XP.

Christophe Nasarre

MSDN Magazine June 2002


Scripting: Windows Script Host 5.6 Boasts Windows XP Integration, Security, New Object Model

  

Windows Script Host (WSH) 5.6, a major upgrade for the WSH environment, provides some significant improvements over previous versions. A brand new security model that is tightly integrated with security in Windows XP allows administrators to place fine-grained restrictions on scripts reducing the risk from malicious code. In addition, local scripts can now run on remote machines, and enhancements to the object model reduce the amount of boilerplate code needed when writing professional code. This overview of WSH 5.6 explains these changes and how .NET and scripting work together.

Dino Esposito

MSDN Magazine May 2002


COM+ 1.5: Discover Powerful Low-Level Programming in Windows XP with New COM+ APIs

  

The new version of COM+ that ships as part of Windows XP includes APIs for low-level context programming. These functions allow you to create contexts that use COM+ runtime services, independent of objects and without registering anything in the COM+ Catalog. Designed for advanced COM+ developers who understand the COM+ context model, these APIs make it easy to integrate runtime services with code in nonstandard ways. This article explains how these low-level context APIs work, discusses when you'd want to use them, and provides a .NET-based wrapper to make it simpler to use the APIs from C#.

Craig Andera and Tim Ewald

MSDN Magazine April 2002


A Simple XML-driven Tool: Monitor Your Web Site's Activity with COM and Active Scripting

  

This article describes a simple Web site monitoring tool built with XML, JScript, Windows Script Host, and COM objects. Although it is not intended to replace complete Web site monitoring software products, it has many useful features that help to keep Web servers up and running. An XML configuration file specifies which Web sites to monitor and the actions to be taken if the site isn't functioning properly. In addition, the tool can be scheduled to run at any specified interval using the Windows Task Scheduler. Functions that probe the sites, log events, and send e-mail notifications are written in JScript.

Panos Kougiouris

MSDN Magazine July 2000


Scripting Windows: Windows Management Instrumentation Provides a Powerful Tool for Managing Windows

  

The new Windows Management Instrumentation (WMI) technology for Windows 2000, Windows NT 4.0, and Windows 98 provides powerful scripting technology that can be used to administrate Windows-based systems. With WMI, you can create scripts to simplify management of devices, user accounts, services, networking, and other aspects of your system. This piece will introduce you to WMI and the WMI Scripting Object Model, taking a look at the available objects, methods, and properties. Along the way, you'll see how these elements can be used to create system management scripts.

Alan Boshier

MSDN Magazine April 2000


Debugging custom task urgent

  

Hi

I want to debug a custom ssis task, I exactly followed the micrsoft paper instuctions. Build and deploy the custom task successfully

I set a break point on InitializeTask method at the beggining then I attached to the devenv.exe(Already dragged a custom task to the scene in a separate vs instace as indicated)

I tried to change the poperties drag another custom component  into the scene but when I turn back to the project where the task source is located then the break point does not recieve the Hit action

How do I to force the break point have the hit in order to step through the code

Thank you  


The complexity resides in the simplicity

trying to use custom assembly with script task in SSIS 2008 - can't find correct version of GACUtil

  

I am trying to use a custom assembly (compiled with VS 2005 framework 2.0) with SSIS 2008.  I understand that I need to put this Assembly in the GAC.  I initially attempted to do this using the GACUtil, but I apparently only have version 1.1 of GACUtil intalled on my development PC.  Shouldn't version 2.0 have been installed as part of VS 2005? 

So I then tried simply copying the dll into the GAC folder using windows explorer.  Well, the dll is now visibly in the GAC folder, but I cannot see it from either VS 2005 or BIDS 2008.  Does that mean I do need to use GACUtil 2.0 or higher to install the DLL into the GAC?  If so, is there any place on the Web that I can download it?


Deploy and update script file with custom ribbon tab to Sharepoint Server 2010

  

Hey everyone,

currently I'm building a custom tab for Sharepoint Server 2010 and at the moment I'm stuck on the following issue,
with the first debug deployment Visual Studio sends the .js file that provides some functions for the ribbon elements from Scripts folder in the VS project
to Sharepoint Server.
However, it won't apply any changes I did on the script afterwards to the file on the server.
So the effect is, that as soon as I do the next debug, the previous script is being used by Sharepoint and the new version, containing the new code, is left aside.

It seems to me as if Visual Studio would only deploy the .js file just once and then rely to this copy, maybe there are some configuration settings to make, but after hours of research, I still can't figure out where things do go wrong or what configuration to apply to update the script on the server.
I couldn't locate the file on hdd either, even searched the whole fs but the results showed only the new script file.

Any help on this would be very much appreciated, this issue drives me nuts and consumes plenty of time ;)

Workaround at the moment: each time the script is changed, set up new project... :D

Greets, Norman

P.S: Yes, I did flush

Deploy and update script file with custom ribbon tab to Sharepoint Server 2010

  

Hey everyone,

currently I'm building a custom tab for Sharepoint Server 2010 and at the moment I'm stuck on the following issue,
with the first debug deployment Visual Studio sends the .js file that provides some functions for the ribbon elements from Scripts folder in the VS project
to Sharepoint Server.
However, it won't apply any changes I did on the script afterwards to the file on the server.
So the effect is, that as soon as I do the next debug, the previous script is being used by Sharepoint and the new version, containing the new code, is left aside.

It seems to me as if Visual Studio would only deploy the .js file just once and then rely to this copy, maybe there are some configuration settings to make, but after hours of research, I still can't figure out where things do go wrong or what configuration to apply to update the script on the server.
I couldn't locate the file on hdd either, even searched the whole fs but the results showed only the new script file.

Any help on this would be very much appreciated, this issue drives me nuts and consumes plenty of time ;)

Workaround at the moment: each time the script is changed, set up new project... :D

Greets, Norman

P.S: Yes, I did flush

How can I create a custom control that adds other controls visible to the page hosting my custom con

  

I want to create a custom control where I define several specifically named DIV sections.  The code-behind logic of the custom control will perform operations on these named DIV sections.  The page where the custom control is hosted needs to be able to add named controls to the DIV sections and perform operations on these named controls added to the DIV sections.

Let me explain a little further.  In the custom control, I want to have code behind logic that fires the following Page Event and uses a condition to make one or another specifically named DIV section visible or not:

    < _
    ToolboxData("<{0}:BaseDetails runat=""server""></{0}:BaseDetails>") _
    > _
    Public Class BaseDetails
        Inherits UserControl

        Protected Sub Page_PreRender(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.PreRender
            DetailsNameDiv1.Visible = False
            DetailsNameDiv2.Visible = False
&nbs

Security problem while debugging Infopath custom code

  

I have made a simple InfoPath formular, and in "Submit Options", checked  "Perform custom action using Code", and write some custom code...

Then i run the debug over this code. The InfoPath formular opened in preview mode, and i could successfully step through InternalStartup method.

I did put some data in fields and clicked on "Submit" button. I expected to be continue debugging at the beging of "FormEvents_Sumbit" method, but i got this error message:

"System.Security.SecurityException
Request for the permission of type 'Microsoft.SharePoint.Security.SharePointPermission, Microsoft.SharePoint.Security, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' failed.
   at TEST_FORM2.FormCode.FormEvents_Submit(Object sender, SubmitEventArgs e)
   at Microsoft.Office.InfoPath.Internal.FormEventsHost.OnSubmit(DocReturnEvent pEvent)
   at Microsoft.Office.Interop.InfoPath.SemiTrust._XDocumentEventSink2_SinkHelper.OnSubmitRequest(DocReturnEvent pEvent)"

After i clicked OK to this error, i got another one, a little different:

"InfoPath cannot submit the form.
The OnSubmitRequest event handler did not work.
Request for the permission of type 'Microsoft.SharePoint.Security.SharePointPermission, Microsoft.SharePoint

Custom DB Installation Issue While Run the Stored Procedure Script

  

1. I have created Custom DB Installation by Installar Class
2. I created Stored Procedure Script From DB
3. Copyied Script in sql.txt
4.Created Custom DB Setup and Executed, But I am getting SP script Execution issue, same script is working in QueryAnalyser Execution

Here is My Execution code

Private

 

Sub ExecuteSql(ByVal DatabaseName As String, ByVal S

Categories: 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend