I believe the URL has changed, so just in case you lost it… Keep track of blog posts from all the DevelopMentor instructors by subscribing to: http://browse.develop.com/bmsfeed/developmentor http://feeds.feedburner.com/DevelopmentorInstructors

Updated 08-19-2009: Feed is now available at: http://feeds.feedburner.com/DevelopmentorInstructors

Next Gig: Tuesday 07/28/2009 6:00 pm - 8:30 pm
Topic: Using Test-Driven Development to Get Done Fast
Presenter: Scott Bressette
Room: Kominsky Auditorium, Husson University, Bangor

Scott walks us through a real life situation to show how using Test-Driven Development gets the code done right the first time. He’ll discuss how understanding Agile concepts such as roles and motives will help you read “between the lines” of what clients are asking for and deliver what they really want. TDD can seem like an impediment to getting things done quickly, but Scott will show how he uses just a few simple techniques to code with both speed and confidence.
Scott is the Director of Development at Occupational Health Research in Skowhegan.

Register at http://www.bangordevelopers.com

I’ve just updated my blog to the latest version of dasBlog and enabled comments again. I picked a new theme (Mads Simple) to freshen things up a little and modified the theme to include a new service offered by DevelopMentor which allows you to browse my blog and that of my fellow DevelopMentor instructors in a great way. Check it out for yourself.

Just got this in the mail:
As you know, Microsoft® Windows 7 was Released to Manufacturing (RTM) this afternoon, July 22, 2009. We are excited to be releasing what we consider our best OS to date and we couldn’t have done it without you, our Technical Beta Testers!
With the announcement of RTM, the beta program is officially closed.

Time to get ready and move my customers to Windows 7

More on availability here: http://windowsteamblog.com/blogs/windows7/archive/2009/07/22/windows-7-has-been-released-to-manufacturing.aspx and http://windowsteamblog.com/blogs/windows7/archive/2009/07/21/when-will-you-get-windows-7-rtm.aspx

Countdown to August 6th has started!

I’ve been using the ReportViewer control in Visual Studio quite a bit to create RDLC (offline) reports that are based on the result of LINQ queries against object trees. It’s been a while since there has been a new release of this control and Visual Studio 2010 did not include anything major with regards to the ReportViewer control. I asked around and got an email from Robert Bruckner answering my two main questions:

1. Yes, the ReportViewer control in VS2010 will run on both .NET 3.5 as well as .NET 4.0.
2. Yes, the ReportViewer control in VS2010 will support Export to Word for RDLC (offline) scenarios.

Thanks Robert (and the rest of the people working on this technology), great news!

I frequently receive emails in my inbox warning me about all sorts of scandals or terrible things that could happen to my health. Usually the person(s) forwarding these mails to me have my best interests at heart. Most of the time the emails are a hoax. I found a good site to check and see whether something is a hoax or not: http://urbanlegends.about.com/

I was hoping to be able to download the RTM version of Windows 7 yesterday, but it looks like I’ll need to be patient a little longer. Brandon LeBlanc explains the RTM process here in a very clear blog post.

I’ve copied the section on how to get it:

Once Windows 7 is complete, how do I get it?

The answer depends on who you are:

• MSDN & TechNet Subscribers: Subscribers will be able to download the final version of Windows 7 a few weeks after we announce RTM.
• Volume License (VL) Customers: As announced today by Bill Veghte during his WPC09 keynote, Windows 7 will be available to Volume License customers on September 1st.
• Consumers, Enthusiasts, & Beta Testers (Everyone else): The retail version of Windows 7 will be available in stores October 22nd. If you pre-ordered Windows 7, it should be delivered sometime around the October 22nd timeframe (depends on the retailer). You can pre-order Windows 7 today through many online retailers like the Microsoft Store.
• On New PCs: OEMs are expected to start shipping new PCs with Windows 7 pre-installed on them around October 22nd.

I just read this post by Paul Gielens (http://weblogs.asp.net/pgielens/archive/2009/05/06/why-asp-net-mvc.aspx) about why a group of developers decided to use ASP.NET MVC.

The answer to the question “what made you guys decide to use MVC for this applications” was interesting “because we wanted to learn something new, and because it’s cool!”.

So the feedback on this post ranges from “ahumpff” to “these guys should not be experimenting when someone else is footing the bill”.

I’d just like to pitch in:

a) It’s great to see people showing interest in new technologies. I’d rather have some folks on my team who are eager to dive into a new technology than those who shy away from anything new.
b) There is not a lot of additional info: but assuming that the project was not a multi-million dollar project and there was some room for a little risk. Then “why not?”. In my experience you can play with any technology, but you won’t truly learn it until you have a serious goal. Without a fixed goal you won’t find the pain points of the technology.
c) I believe in risk driven project management. I’m not sure whether it is an official approach to project management. But I like to list all known risks, then decide whether something needs to be done to mitigate the risk. If the cost of mitigation outweighs the risk, then agree to do nothing. In essence, just about everything in PM is about risk management. Anyway, back to the new technology: do an assessment: will this new technology cost me more time to develop this app? Yes/no? No, then use it. Yes? How much? Can we afford to spend X hours on learning? Will it make my team happy? Happy coders write more code… aw heck, let them use it .

Just ran across the boxes they will be using to ship Windows 7 (available Oct. 22, 2009):

From Bink.nu:
Microsoft has now set July 13th for RTM “sign-off”.

Sign off is the process where all divisions sign that they agree on the final code, which means the actual RTM build will be created a few days earlier, which is targeted on July 10th.

The general availability (GA) is set to October 22nd, this is when you can buy it in stores in a box or on new PC’s (OEM).

We can expect the RTM much earlier on MSDN, Technet and Volume Licensing download sites, probably a few days after July 13th.

Daniel will present at the next Bangor Area .NET Developer (BAND) meeting (June 23rd, 2009):

WPF - A little further down the rabbit hole

Probably most of us have seen at least one slick demo of WPF or Silverlight. Such demos are inspiring, but they don't convey what it's like to actually use WPF in the real world. Fresh from completing our first business-centric application that uses WPF extensively, I'm excited to share from my experience of using WPF in the real world.

Daniel is a developer for Tyler Technologies in Bangor.

More information on: www.bangordevelopers.com

More from Daniel: http://www.danielgpratt.com/

Only one week to go! The MSDN Northeast Roadshow will once again make a stop in Augusta, ME. If you haven’t done so already, then sign up now!

June 18th is the day you can enjoy a day of free learning with Microsoft's New England Dream Team: Chris, Bob & Jim.

More info and sign up info: http://tinyurl.com/Summer09Roadshow.

If you’re planning to use Virtual PC or make use of the XP backwards compatibility mode in Windows 7, then you’ll need to have a CPU that supports hardware virtualization. Sadly is not very clear which CPU’s offer that feature.

I found two pages with useful info, one for Intel processors and one for AMD:

• http://www.tomshardware.com/news/windows-xp-mode-virtualization-intel,7709.html
• http://www.tomshardware.com/news/amd-cpu-windows-xp-mode,7739.html

Note: for XP virtualization you will also need a minimum of 2GB of RAM.

I’ve copied the essential information (including the disclaimer) for your reference pleasure

Disclaimer: I believe this information is accurate, but it is possible that some mistakes may be present in the following tables. caused by inaccuracies in Intel’s documentation or by editing and composition errors. I urge you to do your own research before making any buying decisions. Even if a specific CPU appears to support Intel VT, make sure that the PC’s BIOS manufacturer allows this feature to be enabled.

AMD CPUs

“With the exceptions of Sempron-branded processors and Turion K8 Rev E processors, all notebook processors shipped by AMD include AMD-V and therefore support Windows 7 XP mode."

"With the exceptions of Sempron-branded processors and pre-Rev F Athlon branded processors, all of the desktop processors shipped by AMD include AMD-V and therefore support Windows 7 in XP mode."

"Also, all AMD Opteron processors shipped by AMD from Rev F forward include AMD-V."

Copied from : http://www.proprofs.com/forums/index.php?showtopic=11932

Microsoft 70-536 Objectives

Objectives as updated on Microsoft's Web site: March 29, 2007

Developing applications that use system types and collections
Manage data in a .NET Framework application by using the .NET Framework 2.0 system types (Refer System namespace)

• Value types (More info: Value Types C#)
  • Nullable type
• Reference types
• Attributes (More info: Attributes C# / Attributes Visual Basic)
• Generic types (More info: Generics C# / Generics Visual Basic)
• Exception classes (More info: Exceptions C# / Exceptions Visual Basic)
• Boxing and UnBoxing
• TypeForwardedToAttribute Class:

Manage a group of associated data in a .NET Framework application by using collections. (Refer System.Collections namespace)

• ArrayList class
• Collection interfaces
  • ICollection interface and IList interface
  • IComparer interface and IEqualityComparer interface
  • IDictionary interface and IDictionaryEnumerator interface
  • IEnumerable interface and IEnumerator interface
• Iterators
• Hashtable class
• CollectionBase class and ReadOnlyCollectionBase class
• DictionaryBase class and DictionaryEntry class
• Comparer class
• Queue class
• SortedList class
• BitArray class
• Stack class

Improve type safety and application performance in a .NET Framework application by using generic collections. (Refer System.Collections.Generic namespace)

• Collection.Generic interfaces
  • Generic IComparable interface (Refer System Namespace)
  • Generic ICollection interface and Generic IList interface
  • Generic IComparer interface and Generic IEqualityComparer interface
  • Generic IDictionary interface
  • Generic IEnumerable interface and Generic IEnumerator interface
  • IHashCodeProvider interface
• Generic Dictionary
  • Generic Dictionary class and Generic Dictionary.Enumerator structure
  • Generic Dictionary.KeyCollection class and Dictionary.KeyCollection.Enumerator structure
  • Generic Dictionary.ValueCollection class and Dictionary.ValueCollection.Enumerator structure
• Generic Comparer class and Generic EqualityComparer class
• Generic KeyValuePair structure
• Generic List class, Generic List.Enumerator structure, and Generic SortedList class
• Generic Queue class and Generic Queue.Enumerator structure
• Generic SortedDictionary class
• Generic LinkedList
  • Generic LinkedList class
  • Generic LinkedList.Enumerator structure
  • Generic LinkedListNode class
• Generic Stack class and Generic Stack.Enumerator structure

Manage data in a .NET Framework application by using specialized collections. (Refer System.Collections.Specialized namespace)

• Specialized String classes
  • StringCollection class
  • StringDictionary class
  • StringEnumerator class
• Specialized Dictionary
  • HybridDictionary class
  • IOrderedDictionary interface and OrderedDictionary class
  • ListDictionary class
• Named collections
  • NameObjectCollectionBase class
  • NameObjectCollectionBase.KeysCollection class
  • NameValueCollection class
• CollectionsUtil
• BitVector32 structure and BitVector32.Section structure

Implement .NET Framework interfaces to cause components to comply with standard contracts. (Refer System namespace)

• IComparable interface
• IDisposable interface
• IConvertible interface
• ICloneable interface
• IEquatable interface
• IFormattable interface

Control interactions between .NET Framework application components by using events and delegates. (Refer System namespace)

• Delegate class
• EventArgs class
• EventHandler delegates

Implementing service processes, threading, and application domains in a .NET Framework application
Implement, install, and control a service. (Refer System.ServiceProcess namespace)

• Inherit from ServiceBase class
• ServiceController class and ServiceControllerPermission class
• ServiceInstaller and ServiceProcessInstaller class
• SessionChangeDescription structure and SessionChangeReason enumeration

Develop multithreaded .NET Framework applications. (Refer System.Threading namespace)

• Thread class
• ThreadPool class
• ThreadStart delegate and ParameterizedThreadStart delegate
• Timeout class, Timer class, TimerCallback delegate, WaitCallback delegate, WaitHandle class, and WaitOrTimerCallback delegate
• ThreadState enumeration and ThreadPriority enumeration
• ReaderWriterLock class
• AutoResetEvent class and ManualResetEvent class
• IAsyncResult interface (Refer System namespace)
• EventWaitHandle class, RegisteredWaitHandle class, SendOrPostCallback delegate, and IOCompletionCallback delegate
• Interlocked class
• ExecutionContext class, HostExecutionContext class, HostExecutionContext Manager class, and ContextCallback delegate
• LockCookie structure, Monitor class, Mutex class, and Semaphore class

Create a unit of isolation for common language runtime in a .NET Framework application by using application domains. (Refer System namespace)

• Create an application domain.
• Unload an application domain.
• Configure an application domain.
• Retrieve setup information from an application domain.
• Load assemblies into an application domain.

Embedding configuration, diagnostic, management, and installation features into a .NET Framework application
Embed configuration management functionality into a .NET Framework application. (Refer System.Configuration namespace)

• Configuration class and ConfigurationManager class
• ConfigurationElement class, ConfigurationElementCollection class, and ConfigurationElementProperty class
• ConfigurationSection class, ConfigurationSectionCollection class, ConfigurationSectionGroup class, and ConfigurationSectionGroupCollection class
• Implement ISettingsProviderService interface
• Implement IApplicationSettingsProvider interface
• ConfigurationValidatorBase class

Create a custom Microsoft Windows Installer for the .NET Framework components by using the System.Configuration.Install namespace, and configure the .NET Framework applications by using configuration files, environment variables, and the .NET Framework Configuration tool (Mscorcfg.msc).

• Installer class
• Configure which runtime version a .NET Framework application should use.
• Configure where the runtime should search for an assembly.
• Configure the location of an assembly and which version of the assembly to use.
• Direct the runtime to use the DEVPATH environment variable when you search for assemblies.
• AssemblyInstaller class
• ComponentInstaller class
• Configure a .NET Framework application by using the .NET Framework Configuration tool (Mscorcfg.msc).
• ManagedInstallerClass class
• InstallContext class
• InstallerCollection class
• InstallEventHandler delegate
• Configure concurrent garbage collection.
• Register remote objects by using configuration files.

Manage an event log by using the System.Diagnostics namespace.

• Write to an event log.
• Read from an event log.
• Create a new event log.

Manage system processes and monitor the performance of a .NET Framework application by using the diagnostics functionality of the .NET Framework 2.0. (Refer System.Diagnostics namespace)

• Get a list of all running processes.
• Retrieve information about the current process.
• Get a list of all modules that are loaded by a process.
• PerformanceCounter class, PerformanceCounterCategory, and CounterCreationData class
• Start a process both by using and by not using command-line arguments.
• StackTrace class
• StackFrame class

Debug and trace a .NET Framework application by using the System.Diagnostics namespace.

• Debug class and Debugger class
• Trace class, CorrelationManager class, TraceListener class, TraceSource class, TraceSwitch class, XmlWriterTraceListener class, DelimitedListTraceListener class, and EventLogTraceListener class
• Debugger attributes
  • DebuggerBrowsableAttribute class
  • DebuggerDisplayAttribute class (More info: Using DebuggerDisplay Attribute)
  • DebuggerHiddenAttribute class
  • DebuggerNonUserCodeAttribute class
  • DebuggerStepperBoundaryAttribute class
  • DebuggerStepThroughAttribute class
  • DebuggerTypeProxyAttribute class (More info: Using DebuggerTypeProxy Attribute)
  • DebuggerVisualizerAttribute class

Embed management information and events into a .NET Framework application. (Refer System.Management namespace)

• Retrieve a collection of Management objects by using the ManagementObjectSearcher class and its derived classes
  • Enumerate all disk drivers, network adapters, and processes on a computer.
  • Retrieve information about all network connections.
  • Retrieve information about all services that are paused.
• ManagementQuery class
  • EventQuery class
  • ObjectQuery class
• Subscribe to management events by using the ManagementEventWatcher class.

Implementing serialization and input/output functionality in a .NET Framework application
Serialize or deserialize an object or an object graph by using runtime serialization techniques. (Refer System.Runtime.Serialization namespace)

• Serialization interfaces
  • IDeserializationCallback interface
  • IFormatter interface and IFormatterConverter interface
  • ISerializable interface
• Serilization attributes
  • OnDeserializedAttribute class and OnDeserializingAttribute class
  • OnSerializedAttribute class and OnSerializingAttribute class
  • OptionalFieldAttribute class
• SerializationEntry structure and SerializationInfo class
• ObjectManager class
• Formatter class, FormatterConverter class, and FormatterServices class
• StreamingContext structure

Control the serialization of an object into XML format by using the System.Xml.Serialization namespace.

• Serialize and deserialize objects into XML format by using the XmlSerializer class
• Control serialization by using serialization attributes.
• Implement XML Serialization interfaces to provide custom formatting for XML serialization.
• Delegates and event handlers are provided by the System.Xml.Serialization namespace

Implement custom serialization formatting by using the Serialization Formatter classes.

• SoapFormatter class (Refer System.Runtime.Serialization.Formatters.Soap namespace)
• BinaryFormatter class (Refer System.Runtime.Serialization.Formatters.Binary namespace)

Access files and folders by using the File System classes. (Refer System.IO namespace)

• File class and FileInfo class
• Directory class and DirectoryInfo class
• DriveInfo class and DriveType enumeration
• FileSystemInfo class and FileSystemWatcher class
• Path class
• ErrorEventArgs class and ErrorEventHandler delegate
• RenamedEventArgs class and RenamedEventHandler delegate

Manage byte streams by using Stream classes. (Refer System.IO namespace)

• FileStream class
• Stream class
• MemoryStream class
• BufferedStream class

Manage the .NET Framework application data by using Reader and Writer classes. (Refer System.IO namespace)

• StringReader class and StringWriter class
• TextReader class and TextWriter class
• StreamReader class and StreamWriter class
• BinaryReader class and BinaryWriter class

Compress or decompress stream information in a .NET Framework application (refer System.IO.Compression namespace), and improve the security of application data by using isolated storage. (Refer System.IO.IsolatedStorage namespace)

• IsolatedStorageFile class
• IsolatedStorageFileStream class
• DeflateStream class
• GZipStream class

Improving the security of the .NET Framework applications by using the .NET Framework 2.0 security features
Implement code access security to improve the security of a .NET Framework application. (Refer System.Security namespace)

• SecurityManager class
• CodeAccessPermission class
• Modify the Code Access security policy at the computer, user, and enterprise policy level by using the Code Access Security Policy tool (Caspol.exe).
• PermissionSet class and NamedPermissionSet class
• Standard Security interfaces
  • IEvidenceFactory interface
  • IPermission interface

Implement access control by using the System.Security.AccessControl classes.

• DirectorySecurity class, FileSecurity class, FileSystemSecurity class, and RegistrySecurity class
• AccessRule class
• AuthorizationRule class and AuthorizationRuleCollection class
• CommonAce class, CommonAcl class, CompoundAce class, GenericAce class, and GenericAcl class
• AuditRule class
• MutexSecurity class, ObjectSecurity class, and SemaphoreSecurity class

Implement a custom authentication scheme by using the System.Security.Authentication classes. (Refer System.Security.Authentication namespace)
Encrypt, decrypt, and hash data by using the System.Security.Cryptography classes. (Refer System.Security.Cryptography namespace)

• DES class and DESCryptoServiceProvider class
• HashAlgorithm class
• DSA class and DSACryptoServiceProvider class
• SHA1 class and SHA1CryptoServiceProvider class
• TripleDES and TripleDESCryptoServiceProvider class
• MD5 class and MD5CryptoServiceProvider class
• RSA class and RSACryptoServiceProvider class
• RandomNumberGenerator class
• CryptoStream class
• CryptoConfig class
• RC2 class and RC2CryptoServiceProvider class
• AssymetricAlgorithm class
• ProtectedData class and ProtectedMemory class
• RijndaelManaged class and RijndaelManagedTransform class
• CspParameters class
• CryptoAPITransform class
• Hash-based Message Authentication Code (HMAC)
  • HMACMD5 class
  • HMACRIPEMD160 class
  • HMACSHA1 class
  • HMACSHA256 class
  • HMACSHA384 class
  • HMACSHA512 class

Control permissions for resources by using the System.Security.Permission classes. (Refer System.Security.Permission namespace)

• SecurityPermission class
• PrincipalPermission class
• FileIOPermission class
• StrongNameIdentityPermission class
• UIPermission class
• UrlIdentityPermission class
• PublisherIdentityPermission class
• GacIdentityPermission class
• FileDialogPermission class
• DataProtectionPermission class
• EnvironmentPermission class
• IUnrestrictedPermission interface
• RegistryPermission class
• IsolatedStorageFilePermission class
• KeyContainerPermission class
• ReflectionPermission class
• StorePermission class
• SiteIdentityPermission class
• ZoneIdentityPermission class

Control code privileges by using System.Security.Policy classes. (Refer System.Security.Policy namespace)

• ApplicationSecurityInfo class and ApplicationSecurityManager class
• ApplicationTrust class and ApplicationTrustCollection class
• Evidence class and PermissionRequestEvidence class
• CodeGroup class, FileCodeGroup class, FirstMatchCodeGroup class, NetCodeGroup class, and UnionCodeGroup class
• Condition classes
  • AllMembershipCondition class
  • ApplicationDirectory class and ApplicationDirectoryMembershipCondition class
  • GacInstalled class and GacMembershipCondition class
  • Hash class and HashMembershipCondition class
  • Publisher class and PublisherMembershipCondition class
  • Site class and SiteMembershipCondition class
  • StrongName class and StrongNameMembershipCondition class
  • Url class and UrlMembershipConditon class
  • Zone class and ZoneMembershipCondition class
• PolicyLevel class and PolicyStatement class
• IApplicationTrustManager interface, IMembershipCondition interface, and IIdentityPermissionFactory interface

Access and modify identity information by using the System.Security.Principal classes. (Refer System.Security.Principal namespace)

• GenericIdentity class and GenericPrincipal class
• WindowsIdentity class and WindowsPrincipal class
• NTAccount class and SecurityIdentifier class
• IIdentity interface and IPrincipal interface
• WindowsImpersonationContext class
• IdentityReference class and IdentityReferenceCollection class

Implementing interoperability, reflection, and mailing functionality in a .NET Framework application
Expose COM components to the .NET Framework and the .NET Framework components to COM. (Refer System.Runtime.InteropServices namespace)

• Import a type library as an assembly.
  • Add references to type libraries.
  • Type Library Importer (Tlbimp.exe)
  • Generate interop assemblies from type libraries.
    • Imported Library Conversion
    • Imported Module Conversion
    • Imported Type Conversion
    • Imported Member Conversion
    • Imported Parameter Conversion
  • TypeConverter class
• Create COM types in managed code.
• Compile an interop project.
• Deploy an interop application.
• Qualify the .NET Framework types for interoperation.
• Apply Interop attributes, such as the ComVisibleAttribute class.
• Package an assembly for COM.
• Deploy an application for COM access.

Call unmanaged DLL functions in a .NET Framework application, and control the marshaling of data in a .NET Framework application. (Refer System.Runtime.InteropServices namespace)

• Platform Invoke
• Create a class to hold DLL functions.
• Create prototypes in managed code.
  • DllImportAttribute class
• Call a DLL function.
• Call a DLL function in special cases, such as passing structures and implementing callback functions.
• Create a new Exception class and map it to an HRESULT.
• Default marshaling behavior
• Marshal data with Platform Invoke
• Marshal data with COM Interop
• MarshalAsAttribute class and Marshal class

Implement reflection functionality in a .NET Framework application (refer System.Reflection namespace), and create metadata, Microsoft intermediate language (MSIL), and a PE file by using the System.Reflection.Emit namespace.

• Assembly class
• Assembly attributes
  • AssemblyAlgorithmIdAttribute class
  • AssemblyCompanyAttribute class
  • AssemblyConfigurationAttribute class
  • AssemblyCopyrightAttribute class
  • AssemblyCultureAttribute class
  • AssemblyDefaultAliasAttribute class
  • AssemblyDelaySignAttribute class
  • AssemblyDescriptionAttribute class
  • AssemblyFileVersionAttribute class
  • AssemblyFlagsAttribute class
  • AssemblyInformationalVersionAttribute class
  • AssemblyKeyFileAttribute class
  • AssemblyTitleAttribute class
  • AssemblyTrademarkAttribute class
  • AssemblyVersionAttribute class
• Info classes
  • ConstructorInfo class
  • MethodInfo class
  • MemberInfo class
  • PropertyInfo class
  • FieldInfo class
  • EventInfo class
  • LocalVariableInfo class
• Binder class and BindingFlags
• MethodBase class and MethodBody class
• Builder classes
  • AssemblyBuilder class
  • ConstructorBuilder class
  • EnumBuilder class
  • EventBuilder class
  • FieldBuilder class
  • LocalBuilder class
  • MethodBuilder class
  • ModuleBuilder class
  • ParameterBuilder class
  • PropertyBuilder class
  • TypeBuilder class

Send electronic mail to a Simple Mail Transfer Protocol (SMTP) server for delivery from a .NET Framework application. (Refer System.Net.Mail namespace)

• MailMessage class
• MailAddress class and MailAddressCollection class
• SmtpClient class, SmtpPermission class, and SmtpPermissionAttribute class
• Attachment class, AttachmentBase class, and AttachmentCollection class
• SmtpException class and SmtpFailedRecipientException class
• SendCompletedEventHandler delegate
• LinkedResource class and LinkedResourceCollection class
• AlternateView class and AlternateViewCollection class

Implementing globalization, drawing, and text manipulation functionality in a .NET Framework application
Format data based on culture information. (Refer System.Globalization namespace)

• Access culture and region information in a .NET Framework application.
  • CultureInfo class
  • CultureTypes enumeration
  • RegionInfo class
• Format date and time values based on the culture.
  • DateTimeFormatInfo class
• Format number values based on the culture.
  • NumberFormatInfo class
  • NumberStyles enumeration
• Perform culture-sensitive string comparison.
  • CompareInfo class
  • CompareOptions enumeration
• Build a custom culture class based on existing culture and region classes.
  • CultureAndRegionInfoBuilder class
  • CultureAndRegionModifiers enumeration

Enhance the user interface of a .NET Framework application by using the System.Drawing namespace.

• Enhance the user interface of a .NET Framework application by using brushes, pens, colors, and fonts.
  • Brush class
  • Brushes class
  • SystemBrushes class
  • TextureBrush class
  • Pen class
  • Pens class
  • SystemPens class
  • SolidBrush class
  • Color structure
  • ColorConverter class
  • ColorTranslator class
  • SystemColors class
  • StringFormat class
  • Font class
  • FontConverter class
  • FontFamily class
  • SystemFonts class
• Enhance the user interface of a .NET Framework application by using graphics, images, bitmaps, and icons.
  • Graphics class
  • BufferedGraphics class
  • BufferedGraphicsManager class
  • Image class
  • ImageConverter class
  • ImageAnimator class
  • Bitmap class
  • Icon class
  • IconConverter class
  • SystemIcons class
• Enhance the user interface of a .NET Framework application by using shapes and sizes.
  • Point Structure
  • PointConverter class
  • Rectangle Structure
  • RectangleConverter class
  • Size Structure
  • SizeConverter class
  • Region class

Enhance the text handling capabilities of a .NET Framework application (refer System.Text namespace), and search, modify, and control text in a .NET Framework application by using regular expressions. (Refer System.Text.RegularExpressions namespace)

• StringBuilder class
• Regex class
• Match class and MatchCollection class
• Group class and GroupCollection class
• Encode text by using Encoding classes
  • Encoding class
  • EncodingInfo class
  • ASCIIEncoding class
  • UnicodeEncoding class
  • UTF8Encoding class
  • Encoding Fallback classes
    • EncoderFallback
    • EncoderFallbackBuffer
    • EncoderFallbackException
    • EncoderReplacementFallback
    • EncoderReplacementFallbackBuffer
    • EncoderExceptionFallback
    • EncoderExceptionFallbackBuffer
• Decode text by using Decoding classes.
  • Decoder class
  • Decoder Fallback classes
    • DecoderFallback
    • DecoderFallbackBuffer
    • DecoderFallbackException
    • DecoderReplacementFallback
    • DecoderReplacementFallbackBuffer
    • DecoderExceptionFallback
    • DecoderExceptionFallbackBuffer
• Capture class and CaptureCollection class

Today I’m switching my default search provider in Internet Explorer over to the new Microsoft Search Engine: Bing.

It seems fast, perhaps even faster than Google and with the few searches I’ve done it seems to provide the right results.

Did some quick looking around, there is a Bing developer page and Bing API as well.

Links:

• Bing: www.bing.com
• Bing Developer Center: http://www.bing.com/developers/
• Bing API: http://msdn.microsoft.com/en-us/library/dd251056.aspx
• Bing SDK (beta): http://www.microsoft.com/downloads/details.aspx?FamilyId=0F513086-078B-47A8-A889-842DC93A69AB&displaylang=en

I guess the success for LINQ to SQL makes it hard for Entity Framework to absorb the full feature set in a single (v2) release. The team has been working on a bunch of fixes and improvements to be delivered in .NET 4.0.

Here is the list as posted by Damien:

LINQ to SQL changes in .NET 4.0

Change list

Performance

• Query plans are reused more often by specifically defining text parameter lengths
• Identity cache lookups for primary key with single result now includes query.Where(predicate).Single/SingleOrDefault/First/FirstOrDefault
• Reduced query execution overhead when DataLoadOptions specified (cache lookup considers DataLoadOptions value equivalency – post beta 1)

Usability

• ITable<T> interface for additional mocking possibilities
• Contains with enums automatically casts to int or string depending on column type
• Associations can now specify non-primary-key columns on the other end of the association for updates
• Support list initialization syntax for queries
• LinqDataSource now supports inherited entities
• LinqDataSource support for Dynamic Data query extenders added

Query stability

• Contains now detects self-referencing IQueryable and doesn't cause a stack overflow
• Skip(0) no longer prevents eager loading
• GetCommand operates within SQL Compact transactions
• Exposing Link<T> on a property/field is detected and reported correctly
• Compiled queries now correctly detect a change in mapping source and throw
• String.StartsWith, EndsWith and Contains now correctly handles ~ in the search string
• Now detects multiple active result sets (MARS) better
• Associations are properly created between entities when using eager loading with Table-Valued Functions (TVFs)
• Queries that contain sub-queries with scalar projections now work better

Update stability

• SubmitChanges no longer silently consumes transaction rollback exceptions
• SubmitChanges deals with timestamps in a change conflict scenario properly
• IsDbGenerated now honors renamed properties that don't match underlying column name
• Server-generated columns and SQL replication/triggers now work instead of throwing SQL exception

General stability

• Binary types equate correctly after deserialization
• EntitySet.ListChanged fired when adding items to an unloaded entity set
• Dispose our connections upon context disposal (ones passed in are untouched)

SQL Metal

• Foreign key property setter now checks all affected associations not just the first
• Improved error handling when primary key type not supported
• Now skips stored procedures containing table-valued parameters instead of aborting process
• Can now be used against connections that use AttachDbFilename syntax
• No longer crashes when unexpected data types are encountered

LINQ to SQL class designer

• Now handles a single anonymously named column in SQL result set
• Improved error message for associations to nullable unique columns
• No longer fails when using clauses are added to the partial user class
• VarChar(1) now correctly maps to string and not char
• Decimal precision and scale are now emitted correctly in the DbType attributes for stored procedures
• Foreign key changes will be picked up when bringing tables back into the designer without a restart

Code generation (SQL Metal + LINQ to SQL class designer)

• Stored procedures using original values now compiles when the entity and context namespaces differ
• Virtual internal now generates correct syntax
• Mapping attributes are now fully qualified to prevent conflicts with user types
• KnownTypeAttributes are now emitted for DataContractSerializer with inheritance
• Delay-loaded foreign keys now have the correct, compilable, code generated
• Using stored procedures with concurrency no longer gets confused if entities in different namespace to context
• ForeignKeyReferenceAlreadyHasValueException is now thrown if any association is loaded not just the first

Potentially breaking changes

We worked very hard to avoid breaking changes but of course any potential bug fix is a breaking change if your application was depending on the wrong behavior. The ones I specifically want to call out are:

Skip(0) is no longer a no-op

The special-casing of 0 for Skip to be a no-op was causing some subtle issues such as eager loading to fail and we took the decision to stop special casing this. This means if you had syntax that was invalid for a Skip greater than 0 it will now also be invalid for skip with a 0. This makes more sense and means your app would break on the first page now instead of subtlety breaking on the second page. Fail fast :)

ForeignKeyReferenceAlreadyHasValue exception

If you are getting this exception where you weren’t previously it means you have an underlying foreign key with multiple associations based on it and you are trying to change the underlying foreign key even though we have associations loaded.Best thing to do here is to set the associations themselves and if you can’t do that make sure they aren’t loaded when you want to set the foreign key to avoid inconsistencies.

I’m playing around with code generation using Visual Studio 2008 T4 and I needed to pull in some data. Easiest way to create the data is using Excel and then pull it into a dataset. Using the right connection string this becomes very easy.

The code below shows how to select the data from a worksheet.

public class Excel2007Reader

{

    private static string BuildExcelConnection( string filename )

    {

        return @"Provider=Microsoft.ACE.OLEDB.12.0;Data Source=" + filename + @";Extended Properties=""Excel 12.0;HDR=YES;""";

    }

    public static DataSet Read( string filename, string worksheet, string range, string tableName )

    {

        DataSet result = new DataSet();

        string connectionString = BuildExcelConnection( filename );

        string select = @"SELECT * FROM [" + worksheet + "$" + range + "]";

        using ( OleDbConnection conn = new OleDbConnection( connectionString ) )

        {

            conn.Open();

            using ( OleDbCommand cmd = new OleDbCommand( select, conn ) )

            {

                OleDbDataAdapter da = new OleDbDataAdapter( cmd );

                da.Fill( result, tableName );

            }

            conn.Close();

        }

        return result;

    }

}

News travels fast in todays world of digital information. Blogs, Forums, Facebook and Twitter allow for easy and quick repetition of a bit of information. Heck twitter even has a name for it ‘retweeting’ (look for the posts that start with RT). I guess not so long retweeting would have been called gossiping. However, just as in real life you can’t always believe everything somebody tells you. Sometimes you need to check to make sure the information you’re getting is true. Because yes, not everything that is repeated, retweeted or posted is always true. Yesterday Ted Neward fell prey to believing someone he received an email from and responding by posting a response on his blog. Now why would I care? Well, the email Ted got told him that DevelopMentor was bye bye… As a former instructor at DevelopMentor Ted felt sad and wanted to pay homeage to the “many good people” at DevelopMentor. As it turns out the email Ted received contained false information, but within minutes of posting the blog entry information was spreading (I believe the word is ‘virally’) across the Internet with re-tweets and all those other forms of digital goodness spreading this piece of false information almost at the speed of light.

Now the good news is that DevelopMentor is very much alive and kicking and that the “many good people” that Ted paid homage to are working there today. They are teaching classes, helping customers be all that they can be. And not just with teaching classes, but also with onsite training, consulting on projects and also with the new Remote Access Open Enrollment Courses*.

Upcoming classes include:

June 15 Essential C# in LOS ANGELES

June 15 Essential Windows Communication Foundation in BOSTON

June 22 Essential Windows Presentation Foundation in BOSTON

More information can be found at www.develop.com

If you don’t believe me, or want to check the facts then call 800.699.1932 right now and register for a class! You can also email requests@develop.com

* Save Time and Travel: Remote Access Open Enrollment Courses

You can now take open enrollment courses in our Los Angeles and Boston facilities without traveling. Remote Access to our ongoing schedule of instructor-led courses will allow you to fully participate real-time in expert-level lectures, demos and labs that have made DevelopMentor a leader in software development training. We've added new collaboration tools and prepared our instructors for remote students in class so you will be fully engaged in the learning process.

In our Maine Microsoft Certification Study Group we recently had a discussion about using regular expression. Today I found myself writing a RegEx to check for illegal characters in a formula (string). I thought I’d share the solution:

private bool FormulaContainsIllegalCharacters( string formula )

{

    bool result = false;

    try

    {

        Regex r = new Regex( @"(!)|(@)|(#)|(\$)|(%)|(&)" );

        result = r.Match( formula ).Success;

    }

    catch { } // ignore any regular expressions errors -> return false

    return result;

}

In my case I’m not interested in handling exceptions. If a technical error occurs I will accept the input. Notice that I needed to put a “\” before the $ sign, since the $ is a reserved character marking the end of a line.
I don’t need to put each character in “( )” brackets, but for personal preference I just find it easer to read.

Whenever I need one I always need search for a good ASII table.

So here is one:

On June 26th the SDN will organize it’s quarterly Software Development Event in Hotel Houten (te Houten) in the Netherlands.

The speaker line-up is awesome (as usual), don’t miss it!

Sessions:

Sign up here: www.sdn.nl/sde