While it all makes sense now, it didn’t make sense when I first saw this warning message: Warning 304 The version of the .NET Framework launch condition ‘.NET Framework 4 Client Profile’ does not match the selected .NET Framework bootstrapper package. Update the .NET Framework launch condition to match the version of …
Category: .NET Framework
The remote server or share does not support transacted file operations
Despite its pitiful adoption in the developer community, I am implementing Transactional NTFS (TxF) transactions using the Microsoft.KtmIntegration.TransactedFile class. This allows me to reap the benefits of TransactionScope and distributed transactions for file operations (e.g. creates, updates, deletes). This is the only missing piece for typical transactional business applications. With …
Continue reading “The remote server or share does not support transacted file operations”
Gearing up for Juval Lowy’s Architect’s Master Class
The sole 2010 offering in the USA of IDesign‘s Architect’s Master Class conducted by the man himself, Juval Lowy, is only a few weeks away. I checked in at the IDesign web site, and found some updates the world needs to see. The IDesign C# Coding Standard – updated for .NET …
Continue reading “Gearing up for Juval Lowy’s Architect’s Master Class”
WIF FTW
I’ve been talking about Geneva for a long time. I got the basics down earlier in the year. I tried to come up with my own set of sample apps, but failed to get anywhere. With the official release, and renaming to Windows Identity Foundation (WIF), I have renewed inspiration. …
NetTcpBinding and SecurityNegotiationException “A call to SSPI failed”
Using the NetTcpBinding on a WCF service is secure by default. Unless you override the default settings, you will enjoy Transport Security using Windows authentication and the EncrpytAndSign protection level. When you create a new WCF service library, Visual Studio creates a config file with the following identity block: …
Continue reading “NetTcpBinding and SecurityNegotiationException “A call to SSPI failed””
The WCF Master Class
I was privileged to attend the IDesign WCF Master Class last week. It only comes to the USA one time each year, and is presented by the one and only Juval Lowy. The class is held at the training center on the Microsoft Silicon Valley campus in Mountain View, CA. …
2009 Jacksonville Code Camp: Slides and Code
The 2009 Jacksonville Code Camp was a great success. Many thanks to Bayer, Brandy, and everyone else that made it happen. The bar has been set really high for future Jacksonville code camps, and for the rest of Florida too. My session on Transactional WCF Services went well. Many great …
Continue reading “2009 Jacksonville Code Camp: Slides and Code”
Developers – Get ready for the future!
Important, proven, and universally-useful technologies like WCF and Mobile are still not well-known in the development community. Many believe there is another boom, similar to the 1992 Internet boom, on the horizon that will require skilled and knowledgeable developers to engineer the framework and associated connecting systems. Staying tech-current and …
The flowed transaction could not be unmarshaled.
“Do not anticipate trouble, or worry about what may never happen. Keep in the sunlight.” – Benjamin Franklin It’s obvious that Mr. Franklin didn’t have to deal with bad data, bad code, or even the occasional hiccup. In the real world, there is “trouble” and we need to not …
Continue reading “The flowed transaction could not be unmarshaled.”
Communication with the underlying transaction manager has failed.
Don’t be so quick to blame the service or MSDTC when you see the error “Communication with the underlying transaction manager has failed.” Symptom: An error message that reads something like: System.Transactions.TransactionManagerCommunicationException: Communication with the underlying transaction manager has failed. —> System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from …
Continue reading “Communication with the underlying transaction manager has failed.”