Here is a simple, token-replacement template engine for PowerShell that you might find useful.
One of the problems that framework teams occasionally face on the .NET platform is maintaining the ability to run under partial trust. The most common use of partial trust is by web applications that have been configured to run in medium trust. Under medium trust, certain calls may fail due to more restricted code access security permissions. This includes things like using reflection, accessing environment variables, and file I/O operations on certain paths. This post describes how we test partial trust scenarios on the Entity Framework team.
The other day, I found myself carrying a USB flash drive between two of my computers so that I could continue working on some code that I had been writing. Every time you find yourself touching a USB flash drive, I want you to stop immediately, look into an imaginary camera, and exclaim, “To the cloud!”
This issue has been resolved.
For versions 6.6.3 or newer of Connector/Net, this workaround is not required.
Lately, I’ve taken to using xUnit.net as my unit testing framework of choice for .NET projects. The API is very simple and straightforward as it tries not to re-invent concepts that are already a part of the language. For example constructors and
IDisposableare used instead of some new setup and teardown feature. It also makes great use of generics and lambdas to keep its API surface to a minimum.
I just released another version of my Image Resizer. Here’s a screenshot.
In case anyone missed it, I released a second preview of Image Resizer 3. I wanted to get the existing bits as stable as possible so I fixed a few bugs and created a setup bootstrapper so there is no longer separate 32-bit and 64-bit installers. The main feature I added was multi-threaded resizing so now all those powerful cores on you computer can be used for resizing.
subscribe via RSS