Vincent Van Den Berghe

Subscribe to Vincent Van Den Berghe: eMailAlertsEmail Alerts
Get Vincent Van Den Berghe: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Vincent Van Den Berghe

To solve problems DHTML, JavaScript and XML can't handle, you sometimes need so-called "rich" client components for your Web applications. Traditionally, this is the realm of Java (applets) or ActiveX controls. If your clients are using Internet Explorer 5.5 or higher you have another choice: write your client components in .NET and host them in Internet Explorer. This is an interesting and viable choice if the rest of your development work is also in .NET, since you can use a single technology and a single framework for all your needs, both on the client and the server. This is a good thing, since reducing the number of different technologies reduces some of the development risks and associated costs. Writing .NET components to run on the client is called IE Sourcing. It's not very well documented, and there are a lot of traps and pitfalls if your component does no... (more)

.NET Feature — Writing Client Components in .NET

Determining the Set of Permissions and Creating the Permission Set At this point, we should think about the permissions our component needs. We're creating our own code group and permission set, so we start from scratch: this means that we'll have no permissions at all to start with. So, in addition to the permission to call unmanaged code (which we need to solve the event-handling problem that got us into this mess), we also need to include the permission for our assembly to execute. If we forget to include "execute permission," our component will simply refuse to load. But wait, t... (more)