Pierre Greborio.NET

From Indigo to WCF tool

Ok, my Indigo Proxy Generator is going to be updated to WCF November CTP. I'll change the name to WCF Proxy Generator ;-)

What's new ? From the proxy generator point of view quite nothing, just the code updated to work with the November CTP. The Indigo Service Tester has been posponed until I'll solve several problems with my PropertyGrid ;-)

In the new package I'll add something that I hope you'll find interesting: WCF Unit Test Wizard. That is a Unit Test project (yes, available with Visual Studio Team System/Developer/Tester) which generates the code (proxy class, configuration and test class) to run tests on WCF services. I'm still studying the VS extensions to run a new test project type correctly, I hope to have a first beta next month.

If you ideas or suggestions, please send them to me. Thanks.

Naming Guidelines and Visual Controls

According to the .NET naming guidelines it is often suggested to adopt camel case for private properties/fields and pascal case for protected and public properties/fields.

It is unclear how to name visual controls. Let consider a standard label which is protected in a web form. We could name as following:

1. LblFirstName (classic pascal case for protected fields)
2. StaticFirstName (contro, agnostic version)
3. lblFirstName (as usually I do)
4. _lblFirstName (C++ style)

For read/write controls we could use:

1. TxtFirstName
2. ReadWriteFirstName
3. txtFirstName
4. _txtFirstName

During these last 10 years of development I changed my programming style. I started with 4, then moved to 3. Today I'm thinking about the 2.

VSTO and Security

VSTO (Visual Studio Tools for Office) is a powerful tool used to have the power of .NET framework insode an Office 2003 document (Word, Excel, Outlook and InfoPath).

The only, and most important, limitation I can register is from a security point of view. The documentation says: "To deploy and run an Office solution that uses managed code extensions, you must grant full trust to the assemblies in the security policy of each end user or computer. If the document is in a network location instead of on the user's computer, you must grant full trust to the document as well."

From a policy company point of view its unacceptable to give full trust access to office assemblies. I hope this will change soon...