ClickOnce deployment is another area where Code Access Security needs to be kept in mind. ClickOnce deployments will often be used to deploy Visual Basic .NET (or hybrid Interop Toolkit) applications from a website or network file share. In these cases...

If you recall from an earlier post, I said that the main reason for signing an assembly and giving it a strong name was to prevent it being tampered with. For example, many of the assemblies that make up the .NET framework itself are strong-named assemblies...

The following is an example of how code access security might affect your code when calling unmanaged code. Unmanaged code is a posh way of saying “It isn’t .NET code, it is the stuff you used to write before .NET” :-) In VB6 making a call to a Windows...

For VB6 developers, one area where asymmetric keys and digital signatures cropped up was the requirement to sign downloadable ActiveX controls using Authenticode. The idea was to sign the controls using a digital signature so that the origin of the control...

The second big security area in the .NET framework after Authentication and Authorisation is cryptography. Again, the framework contains a lot of powerful functionality, and again there is an application block that makes it all a bit easier to use. The...

As promised , the first in a series of posts about security relevant to a developer new to .NET (such as a VB6 developer). These are what most people will immediately think of when security is discussed. Authentication This is proving your identity by...

One of the reasons for moving to VB.NET from VB6 may be the more advanced security models available in the .NET Framework - this is particularly relevant in the ASP.NET world where many .NET applications will need a security system. In the desktop arena...

There may be some circumstances where upgrading a VB6 application is not feasible, for example it may rely on a control that simply does not work in the target operating system. I came across a couple of articles on MSDN that discussed the ways that virtualisation...

VB6 programmers will remember a useful little utility called the API Viewer, the helped out when you needed to make a Windows API call. There is now an equivalent tool for .NET, the P/Invoke Interop Assistant ( http://www.codeplex.com/clrinterop ). Not...

I’ve been having a look at some of the samples on the Visual Basic Resource Center to see what’s possible when we start using interop between VB6 and .NET. Here are some of my favourites. This article, “Sharing ADO Recordsets Between Visual Basic 6 and...

Just as an aside - after experimenting with the Interop Forms Toolkit earlier this year I wondered how InteropToolbox ended up in the My namespace – it seems like a useful thing to be able to do. I didn’t have to look far, the answer was in the ActiveXControlHelpers...

A favourite topic for VB6 programmers! Adding a reference to a COM component in Visual Studio adds a reference to a specific version of the VB6 component, so rebuilding the VB6 component without binary compatibility will break the .NET project (you’ll...

How long would it take you to manually convert 50,000 line of Visual Basic 6.0 code to Visual Basic .NET. My guess is… quite a long time :-) However two of the key partners in this space have special versions of their enterprise class tools targeting...

Aberdeen Group have created a new report “ Migrating from VB6 to .NET: The challenge of software agility in a volatile economy ” Some bits that stood out for me: 50% will migrate all the applications, 36% will migrate some (86% in total will migrate)...

Choice in general is a good thing. When faced with moving a Visual Basic 6.0 application to .NET there is plenty of choices to be made. One of those choices is “Which tool should I go with to migrate the code?”. My advice in general is “Try as many as...