Comments
Sort by recent activity
We license the .NET developer bundle, so of course we have Reflector as part of that package, but our relationship with tool providers requires some trust, so that we know we're not going to be screwed in the future.
As others have said, it's not the going-paid-for itself that's important, or the price, it's the lack of principle. At the time Red Gate took over, I reassured other developers who were worried about just this occurring, saying that Red Gate were trustworthy and wouldn't do such a thing. How foolish of me.
I suggest that the only way for Red Gate to mitigate the harm to their reputation will be to make very visible apologies and declarations that this latest announcement was a mistake and open source version 6.
Why open source? The promise was to continue offering a free version for the community. As Red Gate no longer see it as viable to do gratis community work (and this is perfectly fine) the only way they can ensure that a free version is perpetually available is to make it open source. If a closed version of 6, without expiry, is the last free release, then when it stops working due to changes in Windows/.NET, it stops working and the promise is again broken.
While we like Performance Profiler and Memory Profiler, and until now have recommended them, next time we're up for renewal, we'll be looking into competing products. This is not some fit of pique: We simply have to be pragmatic and ensure that our tool support is reliable. / comments
We license the .NET developer bundle, so of course we have Reflector as part of that package, but our relationship with tool providers requires some trust, so that we know we're not going to be scr...