Even with all the community backlash these guys are probably making some bank right now just because people need to get life to move on. NET developers out there and all of them possibly upgrading – that’s a nice chunk of change that Red Gate’s sitting on. In other words Red Gate is trying to make damn sure they’re getting your money if you attempt to use Reflector. There have also been reports of Version 6 installs shutting themselves down and failing to work if the update is refused (I haven’t seen that myself so not sure if that’s true). Not only that but older versions that are already in use also will continually try to update themselves to the new paid version – which when installed will then expire unless registered properly. Not only is Version 7 going to be a paid commercial tool, but the older versions of Reflector won’t be available any longer. Take a look at the message thread that Red Gate dedicated from a link off the download page. People are rabid, and for once I think that this outrage isn’t exactly misplaced. NET community in the most painful way we can?” And that it seems Red Gate has a utterly succeeded. ![]() It’s almost as if somebody in management wrote a slogan: “How can we piss off the. The problem is how Red Gate went about moving the product to commercial which borders on the downright bizarre. NET that’s worth $39 it’s Reflector, right? Ok, so what’s the problem? Why all the fuss? Certainly the $39 Red Gate is trying to charge isn’t going to kill any developer. In short Reflector is an invaluable tool to me. NET components and Reflector has been immensely valuable to me (and my clients) if figuring out exact type signatures required to calling. Even more so recently I’ve been doing a lot of Interop work with a non-.NET application that needs to access. NET Framework, checking out third party code, or verifying some of my own code and resources. Whether it’s for examining the innards of the. NET development that goes by for me where I don’t fire up Reflector. Now normally I’m not one to be critical of companies trying to make money from a product, much less for a product that’s as incredibly useful as Reflector. No more free version - and a shit storm broke out in the community. Then a month back Red Gate started making noise about a new Version Version 7 which would be commercial. NET feature set doesn’t drastically change how types behave. NET 4.0 came out it still continued to work mostly because the. ![]() The product didn’t die and and it didn’t go commercial or to a charge model. Other than the incessant update notices with prominent Red Gate promo on them life with Reflector went on. A lot of ruckus and noise ensued in the community back then about what would happen with the tool and… for the most part very little did. Then about two and a half years ago Red Gate bought the tool from Lutz. Note that you get tons of information about each element in the tree, and almost all related types and members are clickable both in the list and source view so it’s extremely easy to navigate and follow the code flow even in this static assembly only view.įor many year’s Lutz kept the the tool up to date and added more features gradually improving an already amazing tool and making it better. In case you’ve been living under a rock and you’ve never looked at Reflector, here’s what it looks like drilled into an assembly from disk with some disassembled source code showing: Using Reflector you can examine the types in an assembly, drill into type signatures and quickly disassemble code to see how a particular method works. NET Reflector was originally created by Lutz Roeder as a free community tool to inspect. NET devs use at one point or another – decided to change their business model for Reflector and take the product from free to a fully paid for license model. About a month ago Red Gate – the company who owns the NET Reflector tool most.
0 Comments
Leave a Reply. |