Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » DevCenter » Visual Basic .NET   (RSS)

ClickOnce and Security

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,

Introducing code obfuscation

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

Code Access Security in action – calling Unmanaged Code

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

Authenticode and ActiveX controls

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

Cryptography

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

Authentication and Authorisation

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

Aberdeen Group report on Migrating from VB6 to .NET

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)

Visual Basic 6.0 Migration – due diligence is a good thing

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

Results of Visual Basic Survey (UK)

In January we created a survey to understand how folks were using Visual Basic 6.0 and Visual Basic .NET in the UK. This survey was sent out to individuals we “suspected” had Visual Basic 6.0 heritage but it was also widely advertised through the UK MSDN

Visual Basic Upgrade Wizard vs 3rd Party Migration Tools

[If you are UK based, check out www.microsoft.com/uk/vbmigration for more information ] A question I get asked a lot is “Are 3rd party migration tools really that much better than the free upgrade wizard from Microsoft?” Lets me be perfectly candid. Whilst

A mocking framework especially designed for Visual Basic .NET

I was pleased to see the Typemock folks have delivered a special VB.NET API to use Typemock 5.2 for unit testing. This handles the differences in VB9 vs C# 3.0 around Lambdas (VB9 is restricted to functions where as C# 3.0 can handle statement lambdas

New article on extending VB6.0 applications with the Interop Forms Toolkit 2.0

I just wanted to swiftly share some useful links if you choose to extend a Visual Basic 6.0 application including a new article I commissioned in the UK – which turned out rather good. Firstly links to the toolkit download and some of the best existing

Secure your Visual Basic 6.0 investment with Microsoft .NET

[This is currently a UK only initiative but you will still find a lot of useful information on the new site and I know our partners are happy to engage worldwide] Over the last couple of months I have been working with Sarah in my group to pull together

VB6 Interop and TlbImp vs AddRef

I’d always assumed that creating a Runtime Callable Wrapper by adding a reference to the COM component in Visual Studio would generate the same interop code as was generated by using the command line tool TlbImp. That would seem not to be true in at least

Heads up – The VB6 upgrade guide was written before we released the Interop Forms Toolkit

I have been re-reading the ”Upgrading Visual Basic 6.0 Applications to Visual Basic .NET and Visual Basic 2005” guide lately which discusses phased migrations where individual application components are upgraded independently (which I prefer to call “Extending
More Posts Next page »
 
Page view tracker