Free clr software for windows

Debug Inspector 1.23 is a program serving as a Visual Studio Extension (on Visual Studio Gallery), a stand alone Studio EXE to detect unmanaged deadlock. It is soon a SharpDevelop IDE AddIn, that allows you to view the call stacks of multiple threads at the same time, plugs in to the internals of the CLR and automatically detects deadlocks. It allows you to see exactly what the CLR is doing under the hood and shows, for each thread, the monitors (SyncBlock) owned and the monitor waited on, if any.

Enhancements: includes unmanaged DeadLock detection (beta) via the DebugInspector.Studio.exe executable.

Karvonite is a persistence framework for the .NET Framework 2 and it focuses on the manipulation and persistence of .NET objects. This technology will provide a new direction for how small to midsize applications can store and deploy data.
Karvonite is not an O/R mapping tool for a very good reason. There is no relational world to map to. In Karvonite, object data is persisted to an object library.
Karvonite persistence framework is well-suited for creating document centric applications (i.e., a word processor, a game-level editor, game editing tools, configuration files), storing game data, and other kind of applications where XML files are not enough and the horsepower of a SQL engine is unnecessary.
Main features:
- Non-invasive to your code
- Visually define which classes and properties (in your code) you want to persist Supports the .NET Compact Framework
- Requires no interfaces or base classes for persisting objects
- Supports most of the basic CLR types
- Easy deployment
- Framework API with gradual learning curve and very low entry point
- Future support for the Microsoft XNA Framework

This is a fully-functional utility for working with PE/PE +(64bit) files. Including: Editor PE of files, Task Viewer, Win32 PE files optimizer, detector of compiler/packer and many other things.
The basic functions of the program:
Task Viewer
- Process dump
- Dump Full
- Dump Partial
- Dump Region
- Ability to dump .NET CLR processes
- Automatic removal of protection " Anti Dump Protection "
- Change of a priority of process
- Kill process
- Loading of process into PE Editor and PE Sniffer
- Generic OEP Finder
PE Sniffer
- Search of the compiler/packer used
- Ability to update signature base
- Ability to scan directories
- PE Rebuilder
- Optimization of a PE file
- Change of PE address base of a file
PE Editor
- Editing of DOS heading
- Support of new PE+(64bit) format
- CRC correction
- Viewing and editing tables of import/export

Visual C++ 2005 Express Edition enables you to write managed applications for the .NET Framework that take advantage of the vast number of classes in the .NET Framework Class Library, including features such as garbage collection.
The Visual C++ 2005 implements the new ECMA C++/CLI standard for writing simple yet powerful code for the .NET Framework?s Common Language Runtime (CLR). Using Visual C++, you can write class libraries, console applications, or Windows Forms applications. Visual C++ 2005 also lets you use C++ to build 32-bit native code console applications that have access to the full Standard C and C++ libraries. You can also mix native and managed code in a single project, giving you the flexibility to use existing libraries as well as .NET Framework classes in the same application.
Visual C++ 2005 Express Edition includes a fully ISO-compliant implementation of the Standard Template Library (STL). STL is a general purpose library of algorithms and data structures that is based on a concept known as generic programming. The library includes the container classes?such as vector, queue, list, and map?that are implemented using C++ templates. These work with any data type, including both built-in types as well as any types you define yourself.
Main features:
Powerful Language and Libraries
- Create managed and native C++ applications
- Standards conformant, optimizing C++ compiler
- Standard Template Library (STL)
- Use third-party libraries to increase productivity
More Secure C++
- Safe C Runtime Library (CRT)
- Buffer overrun detection
Visually Design Windows Applications
- Visual design surface
- Toolbox
- Property Window
- Snap lines
- Toolstrip control
- Menu control
- Container controls
- WebBrowser control
- MaskedTextBox control
- Background Worker component
- NotifyIcon control
- TreeView control
- ListView control
Interactive Development Environment
- IntelliSense
- XML comments
- Task List
- Find All References
- Navigate code
- Call Browser
Powerful Debugging
- Breakpoints
- Edit and Continue
- Debugger Data Tips
- Debugger Visualizers
- Call Stack
- Conditional Breakpoints
- Breakpoint Window

The Microsoft Management Model Designer (MMD) application was created to be a tool for developing management models The Microsoft Management Model Designer (MMD) application was created to be a tool for developing management models. Management models provide a way to represent all of the areas of manageability for applications and systems services.
You can use the MMD to:
- Build a management framework by defining the managed entities that make up your applications or system services and define how these they relate to each other.
- Import existing instrumentation, such as events and performance counters, into your model.
- Author human-readable knowledge associated with each managed entity, such as event and performance counter descriptions and troubleshooting content.
- Import and export existing MOM 2005 management pack knowledge
- Validate your management model schema.
A health model defines various health states of a system and how that system moves in and out of those health states. It provides a single source for documenting troubleshooting knowledge for an application or service.
A health model describes the following:
- Physical or logical parts of an application or service that an IT Professional (IT Pro) needs to configure, monitor, and report on
- A set of health states the application or service can get into and why
- How to detect and diagnose problems
- How to solve problems
The ultimate goal of creating a health model is to enable the IT Pro to more easily and efficiently maintain systems in a distributed environment. You use the Microsoft Management Model Designer (MMD) to create your health model.
Creating a health model with the Management Model Designer (MMD) includes:
- Building an application structure from predefined components (base classes as defined in the Service Modeling Language Platform) and the relationships between them.
- Building a hierarchy of the logical services and objects the application exposes in a way that is most useful for IT professionals.
- Identifying the functional Aspects for each Managed Entity that are of interest for monitoring.
- Identifying all of the Health States and levels of severity an Aspect can be in.
- Identifying the verification steps that need to be taken to confirm whether an Aspect is in a given Health State.
- Providing the instrumentation that enables the detection of each Health State.
- Identifying the diagnostic steps needed to determine the root cause of the degraded Health State of an Aspect.
- Identifying the recovery steps that need to be taken to resolve a problem and return an Aspect and its parent Managed Entity to full health.
You use the Management Model Designer (MMD) tool to:
- Build a management framework by defining the managed entities that make up your application or system service and define how the entities relate to each other.
- Import existing instrumentation, such as events and performance counters, into your model.
- Enter descriptions and procedures related to Managed Entities for the IT Pro to use for troubleshooting.
- Import and export Operations Manager management pack knowledge.
- Validate your management model.
The Managed Entity framework you create plus the descriptions and procedures you write for each component including Managed Entities, Aspects, Verifiers and Resolvers, become the content for web-based troubleshooting information IT Pros can access through TechNet, as well as output for generating Operations Manager management packs.
System requirements:
- .NET CLR 2.0 and Office Interop Assemblies