Richtlinien und Hinweise fuer Entwickler von Internet Explorer Erweiterungen

Es gibt eine ganze Reihe von Add-on Anwendungen, die den Internet Explorer erweitern. Von Microsoft Support Team wurde nun ein Dokument mit Hinweisen und Richtlinien erstellt, die man beim funktionalen und technischen Entwurf von Internet Explorer Erweiterungen beachten sollte. Das Dokument „Guidelines and requirements for add-ons that extend Internet Explorer” ist unter http://support.microsoft.com/kb/973764 erreichbar und…


SpicIE: New guidance – How to catch and handle Html events in managed Plug-In code

There is a new sample with the name HtmlEvents on the http://code.msdn.microsoft.com/SpicIEContrib page. This sample demonstrates how your managed Plug-In code can register on Html events for specific Html elements. When the registered event is fired then your managed C# will be called. This mechanism could be helpful for the implementation of complex Plug-Ins. The…

1

SpicIE: Deployment of a SpicIE based Plug-In

After you have written a useful plug-in it comes the time when you have to deploy the plug-in on other computers But there may be some pitfalls during the deployment. First there is an “Install.bat” in your project which can be used for the plug-in registration. More difficult is the determination of assemblies which the…

3

SpicIE: Reducing or switching off all diagnostic messages

The SpicIE framework uses the .NET System.Diagnostics.TraceSource class to output a lot of information during the runtime. During the development and debug process these messages could be really helpful to understand how the plugin works. But there are situations where you want to reduce or switch totally off these messages. With the following line of…


SpicIE: Understanding the browser extension creation model

On the discussion part of the SpicIE home page (http://code.msdn.microsoft.com/SpicIE/Thread/List.aspx) I found an interesting question “Constructor is not called…”. The reason for this scenario is following. If you build IE extensions with SpicIE you finally constructs COM objects which Internet Explorer creates for you. In your code these classes seems to be normal objects. But…

1

SpicIE: Vertical or horizontal toolbar does not appear

When you develop a SpicIE plug-in using Internet Explorer toolbars the next tip could be helpful. Sometimes it seems that a programmed toolbar is not visible or the toolbar does not appear at the Internet Explorer UI. The reason for that may be that another toolbar is already visible in Internet Explorer. Internet Explorer UI…

1

SpicIE: A project with an Output Type of Class Library cannot be started directly.

Sometimes I get a debug start message “A project with an Output Type of Class Library cannot be started directly.”  while developing SpicIE based Internet Explorer plug-ins. It seems that the Visual Studio development environment sometimes forgets the debug settings and without that you get this message box. To start/debug your project again you must…


SpicIE: How to debug/trace a SpicIE plug-in

Plug-in development is not easy because always your code runs inside Internet Explorer. Sometimes the code behaves different in Visual Studio debugger and in undebugged Internet Explorer environment. I try to list some of my best practices of SpicIE plug-in development. Debug settings To successfully debug your plug-in with Visual Studio the project settings has…

3

First steps with “SpicIE – Simple Plug-In Creator for Internet Explorer”

There is a new plug-in framework out there which you can use to easily create browser extensions for Internet Explorer 7/8. To use the SpicIE framework you have to download it from the http://code.msdn.microsoft.com/SpicIE location. The current version is Beta 0.81. If you have installed an older version the new setup first asks you to…

2