Link# episode 3

Latest cool stuff I found on The Web:


  • Windows PowerShell Scripts Repository

    The Script Repository categorizes the best sample scripts designed to run on Windows 2000, Windows XP, and Windows Server 2003. The categories listed below connect you to sample scripts written using Windows PowerShell.

  • Microsoft CRM JavaScript snippets

    I noticed that the articles dealing with JavaScript code are your favorite topics, so I decided to have a look at all of my posts in the Microsoft CRM newsgroups dealing with JavaScript samples. I found quite a lot of them, so instead of repeating some common solutions over an over, I’m including them on this page for easy access. Hope you find it helpful.

  • Strong name an Assemblies which uses ActiveX

    If you try to strong name an .NET assembly which uses an ActiveX component, you will receive the following error message: Assembly generation failed — Referenced assembly ‘AxInterop.SHDocVw’ does not have a strong name Now, what can you do to avoid this error? The solution is very easy. You can’t strong name the ActiveX component, but it is possible to strong name the Interop assembly.

  • Top 10 Ways to Motivate Geeks

    Being a geek myself, I think this is a subject I think needs to penetrate all levels of management in every company that values their geeks. By no means is this a rant, but for the last 10 years I’ve seen what motivates us and what doesn’t. I’ve seen the managers that just don’t get it. I’ve seen those that understand completely and react accordingly. So, I thought I’d share my observations and see what everyone has to add as well.

  • SharePoint Server 2007 Resource Links

    A really extensive resource list. Check it out.

  • Hawkeye – The .Net Runtime Object Editor

    Hawkeye is the only .Net tool that allows you to view, edit, analyze and invoke (almost) any object from a .Net application. Whenever you try to debug, test, change or understand an application, Hawkeye can help. With a unique option to Attach to any running .Net process, Hawkeye offers an impressive set of functionalities seen in no other product. Plus … it’s FREE.

  • Adaptive Object Models

    Abstract: We have noticed a common architecture in many systems that emphasize flexibility and run-time configuration. In these systems, business rules are stored externally to the program such as in a database or XML files. The object model that the user cares about is part of the database, and the object model of the code is just an interpreter of the users’ object model. We call these systems “Adaptive Object-Models”, because the users’ object model is interpreted at runtime and can be changed with immediate (but controlled) effects on the system interpreting it. The real power in Adaptive Object-Models is that the definition of a domain model and rules for its integrity can be configured by domain experts external to the execution of the program. These systems are important when flexibility and dynamic runtime configuration is needed, but their architectures have yet to be described in detail. This paper describes the Adaptive Object-Model architecture style along with its strengths and weaknesses. It illustrates the Adaptive Object-Model architectural style by outlining examples of production systems.

  • Reflective Program Generation with Patterns

    Runtime reflection facilities, as present in Java and .NET, are powerful mechanisms for inspecting existing code and metadata, as well as generating new code and metadata on the fly. Such power does come at a high price though. The runtime reflection support in Java and .NET imposes a cost on all programs, whether they use reflection or not, simply by the necessity of keeping all metadata around and the inability to optimize code because of future possible code changes. A second—often overlooked—cost is the difficulty of writing correct reflection code to inspect or emit new metadata and code and the risk that the emitted code is not well-formed. In this paper we examine a subclass of problems that can be addressed using a simpler mechanism than runtime reflection, which we call compile-time reflection.We argue for a high-level construct called a transform that allows programmers to write inspection and generation code in a pattern matching and template style, avoiding at the same time the complexities of reflection APIs and providing the benefits of staged compilation in that the generated code and metadata is known to be well-formed and type safe ahead of time.

  • .NET naked – See these hitherto unpublished pictures of the .NET Framework architecture

    Cool! .Net Framework metrics analyzed.

  • Understanding the TypeDescriptor: A Metadata Engine for Designtime Code

    Great post on TypeDescriptor and his functionalities, even those not related to design time.




Share this post: Email it! | to! | digg it! | reddit! | Furl it! | to any service


~ by Matteo on September 18, 2006.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: