We deployed the latest version of CodePlex software today. This release changes how the Patches feature works for Mercurial based projects by replacing it with Forks. A Fork is a branch of the project repository stored on our servers where you can make modifications and then the project owners can merge your changes back to the main project repository. If you are a Mercurial project owner, and need to get access to unapplied patches, please contact us.

Creating Forks / Pull Requests

The following steps are applicable to all registered CodePlex users.

Step 1: Create a new Fork of a Project

Go to the Source Control tab of a Mercurial project. And click on the “Create Fork” link. Specify a name that will distinguish your intentions, and optionally enter in a description of what the fork is used for.

Once the fork has been created, you’ll be redirected to the “My Forks” view of that project. At this point, you can toggle the view to see “All Forks” or “My Forks” (the toggle will only be visible if you have existing forks in the project).

Step 2: Fork Clone, Commit, and Push

On the page listing for the forks, you will see a Clone URL.

Use your favorite Mercurial tool (we recommend TortoiseHg), to create a local clone of the repository.

Since this is your repository, you have full capabilities of committing locally, and pushing changes back up to the central server. This is a key distinction for forks, as the changes in your fork ARE NOT pushed into the central project repository.

Step 3: Create a Pull Request

Once you have pushed all of your changes to your fork (as well as making sure you have pulled the latest changes from the central repository), you’re ready to create a pull request. When viewing “My Forks”, you’ll see some actions. Click on “Send Pull Request”, enter your comments and click “Send”.

At this point, your pull request is waiting to be applied by project coordinators or developers. Once they have applied or denied your pull request, you will receive an email with their comments.

Applying Pull Requests

The following steps are applicable to project coordinators or developers for a project only.

Step 1: Reviewing / Apply Pull Request

As a project contributor, when you visit the forks page, you’ll see that you have the ability to subscribe to pull request notifications. When a user submits a pull request, you’ll receive an email with their comments and a link to the Fork.

Once a pull request has been submitted, you’ll want to pull those changes into your local project repository. Note: It is recommended that you get fresh clone in case you wish to not accept the changes.

Once pulled, click the Refresh button in the Repository Explorer to see the new changeset(s).

At this point, you should review the changes and determine if you’d like to accept them. If you do not wish to accept the changes, you can simply delete your local repository and re-clone it. If you do accept the changes, push them to the central project repository.

Step 2: Closing the Loop

No matter if you applied or declined the pull request, you should close the loop. This gives the user the reassurance that the pull request was noticed and acted upon. To do this, visit the Forks page again. You’ll notice that we pop all pending pull requests on to the top so it’s easy to get access to them. Find the pull request you just applied, and click “Apply Pull Request”. Type a message and click Send.

Note: It’s courteous to give really good feedback when declining a pull request. The user is now able to send another pull request with new changes they’ve made to their fork.

This is to announce PostSharp 2.0 CTP 4, available for download today. As most our efforts this month have gone to release the company and the new web site, there is no large increment in this build. However, there are two features that could not wait any more:

1. No more time bomb. All previous releases were hard-coded to expire at a fixed date. This new CTP includes the final licensing system: after a 45-days evaluation period, then you have to choose between the Community Edition and the Professional Edition (and in both case enter the license key). There’s currently no way to get a Community Edition license from the web site; we’ll address that during the next weeks.
2. Support for .NET 4.0 RC and Visual Studio 2010 RC instead of beta 2. Also, the current version should survive better an upgrade to .NET 4.0 RTM unless they break something.

Note that the licensing system itself is beta, so to know which features are enabled/disabled, please refer to our comparison sheet and report any difference with the implementation.

The next milestone for us is to complete online processes (acquisition of commercial and community licenses). Then the rush will be over, and I’ll be able to prepare a RC with rest, calm and serenity :).

Happy PostSharping!

-gael

I am excited to announce the ongoing commercial launch of SharpCrafters, the new company behind PostSharp. As we launched our new web site http://www.sharpcrafters.com/ earlier this week, we decommissioned the domain postsharp.org. The old web site has been serving the project and the community for the last five years.

Thanks for you support!

This is a major step in the life of PostSharp and it’s community of users. For the last 18 months, as the project has grown and got adopted by a raising community of professional developers, it became clear that we had to switch to a commercial model. As the attempt to make a living from services proofed unrealistic, there was only one option left: to make a living from the sales of licenses, which meant to abandon the open-source model. I must insist to all people whose this decision will make angry or disappointed (a minority, I think, yet possibly vocal): going commercial was the only option if PostSharp were to survive.

In this important moment, let me say a couple of words in personal name.

I am extremely thankful for the support I got from the community. Thank you to the thousands of people who downloaded PostSharp and spent time and energy to integrate it in their project. I am fully aware of the risks and costs of early adoption. Thank you to the hundreds who have taken the time to describe their problems the support forum so that I could make the software better. Thank you to companies who have supported the project financially, either by doing business with me or by making important sponsorships or donations, and especially: Starcounter, X-tensive.com, Omicron and a couple of other I am not allowed to name (thank you, David, Daniel, Peter and Yoav). Thank you Carl and Richard from .NET Rocks for the boost you gave to the project before it got any hype. Thank you Ralf Westphal for your extraordinary and sustained help to introduce me to conferences and magazines. Thanks to all guys who presented PostSharp at conferences or invited (particularly Olaf, Michal, and Szymon). Finally, thanks to the dozens and dozens bloggers who shared their enthusiasm.

It’s only because of your joint support that I found the energy, during these 5 years, to strive for the project.

Introducing SharpCrafters

SharpCrafters is the new company behind PostSharp. SharpCrafters has been founded in September 2009 as a limited company of Czech right.

I am especially proud to announce that Roman Stanek accepted to be a private investor and board member at SharpCrafters. Roman is a veteran startup founder. He is the Founder and CEO of Good Data, a SaaS business intelligence platform. Roman was the Founder and CEO of NetBeans (acquired by Sun Microsystems) and Systinet (acquired by Mercury Interactive and later Hewlett Packard). Roman joined our venture in September 2009.

I warmly introduce Vaclav Svacek, who became managing director of SharpCrafters in January 2010. Before joining SharpCrafters, Vaclav was a Technical Team Lead and Solution Architect at Husky Energy, Canada. Vaclav will now concentrate on operations of the company so I can concentrate on what I am good in: programming. Vaclav, I wish you a lot of courage and perseverance, as taking over a one-man business is not the easiest thing on earth (especially if this one man is as stubborn as I am).

So that’s our team today: two full-time employees (me and Vaclav), and a business angel somewhere between the azure and the clouds of California.

Our short-term business objective is to grow from organic resources to a team of 5, which would be a sustainable size to develop and maintain our product… and would allow me to take some rest. We hope to reach this size within one year. Then, we’ll have the ground to think about further developments and products.

Our Business Model

SharpCrafters is a product company. We provide support services to our products, but we don’t live from services themselves. We believe in win-win deals. When a product is good, both customers and publishers are happy, because none looses time in troubleshooting. From a customer’s point of view, contacting support is a defeat. Living from services is like making profit from the unhappiness your customers. It can’t work (unless your customers are unhappy from someone else’s product).

We want to sell licenses of PostSharp (and other products, in the future) to companies who use it for serious business, and we want these customers to be satisfied. We want to continuously improve the quality of our product so that the time our customers and us spend in support and troubleshooting is minimized.

We want people to learn or experiment with aspect-oriented programming – and we don’t want money from them.

Therefore, we have two editions of PostSharp:

• The Community Edition is free of charges and has a limited set of features.
• The Professional Edition is fully functional and we charge money for it.

How much do we charge? Less than Resharper. See our price list. We have license types for all sizes: personal, commercial, corporate site, corporate global. There’s an optional Support Subscription including free major upgrades and priority support (see our web site for details).

Students, teachers, bloggers… can request free licenses. I repeat: we don’t want your money if you’re not doing serious business with PostSharp. (Oh yes, disclaimer: there is no right to a free license; SharpCrafters will grant them at its sole discretion according to the information provided by the requestor and the information that can be publicly gathered on the web.)

Finally, our business model favors redistribution of PostSharp by third parties, and we’ll make sure that our offer is very affordable to startups.

What’s Next?

There’s still a lot to do before the commercial launch is complete. The next milestones are the following:

1. Later this week, we’ll publish a new CTP without hard-coded timebomb and with support for Visual Studio 2010 RC. This new release will support license keys, which means that you can start to purchase licenses :).
2. Then, we will update our web site so that you can acquire license keys online. (Currently, we only support manual orders).
3. I need to blog about our legacy policies for PostSharp 1.5.
4. Finally, we need to complete PostSharp 2.0.

Your Opinion Is Important

We are eager to hear from you. If you have any issue or question with our licensing and pricing model, if it’s just “not working for you”, chances are great that other have the same issue, and we will gladly attempt to address it.

Happy PostSharping!

-gael

Do you have a passion for open source and want to help shape the direction of CodePlex? Do you love delivering customer-focused products? Are you interested in working with a small, high performance team in an agile environment? Then you should consider being the CodePlex Program Manager!

We deployed the latest version of the CodePlex software today.

Associating Change sets to Releases

When you’re editing your release information, you’ll notice a new textbox in the Release Details section that will allow you to add a Change set number.

Just type in a valid change set number from your source control listing, and click the Save button. You’ll notice that when you view your release later, you’ll see that there is now a link pointing directly to that change set.

To complete the cycle, when viewing your list of change sets, we’ll highlight the specific change set and give a link back to the release.

Displaying Mercurial Branches and Tags

With the recent support of Mercurial as a supported source control system, we have realized there are still lots of room for improvement for to host a great experience. Our first of many features to come to directly support Mercurial within CodePlex was the display of branches and tags on the change set listing.

To ensure that existing Mercurial users quickly understood how branches and tags are displayed, we adopted the display you commonly see in VisualHg. Branches are indicated in green, and Tags are indicated in yellow. Furthermore, you’ll also notice that we are not displaying the branch name for each change set, but only when there is a context switch between branches.

When you drill-down into a change set to view files, you will also notice the display of branches and tags. At this level, we will always display a branch so there is no confusion.

Where can I see an Example?

You can visit CodePlex’s wiki engine, WikiPlex, where I set the change set numbers for all releases and Mercurial as a source control system showing branches and tags.

I created my first account on CodePlex back in January 2006, over 4 years ago, when the site was still in an alpha internal-only preview. Shortly after playing with the initial UI, I sent the CodePlex team a 15 page document on all the UI suggestions I had. Little did I know that just a couple years later I would be reviewing the CodePlex UI as my day job. Needless to say, I’ve felt like a member of the team for a very long time.

This Friday, February 5, will be my last day as the Program Manager for CodePlex. I’ve accepted a position as Developer Evangelist at Microsoft’s Silicon Valley campus in California. You can follow my adventures on my MSDN blog at http://blogs.msdn.com/saraford.

It’s been a tremendous experience being the PM for Microsoft’s Open Source project hosting site, watching almost 11,000 new open source projects get created since I officially joined the team in October 2007. I want to thank everyone in the CodePlex community for such a fascinating 4 years.

And since it is Carnival back home in New Orleans, I’ll leave you all with “Laissez-les bons temps rouler! Geaux Saints!”

I am happy to announce the release of PostSharp 2.0 CTP 3, available for download today.

This is principally a bug fixing release, since more than 40 issues have been solved. The most significant improvement is the Customer Experience Improvement Program (CEIP): the feature, fully opt-in, is able to automatically report unhandled exceptions in PostSharp, and collects some anonymous usage statistics. The CEIP has been included in an intermediate build between CTP 2 and CTP 3, and most issues solved in CTP have actually been reported by the CEIP. For uploading, our implementation uses Microsoft BITS, a background installed with Windows, so the process never interupts your work and does not consume the bandwidth when you're using it (and it very scalable on our server ;).

Except that, sadly enough, there has been no progress in features. We have been fully busy preparing the launch of the new company and the new web site. I'm glad to say that, although we are a couple of weeks late on the technical point, we made good progress with commercial stuff. You'll hear more about that in a couple of weeks.

Just as in CTP 2, the following features are not included in CTP 3 but are planned for a future preview of 2.0:

• Conceptual Documentation;
• Reference Documentation and Conceptual Documentation of PostSharp SDK (previously PostSharp Core);
• Support for Silverlight and Compact Framework.

This release is hardcoded to expire on March 1st, 2010, and in the mean time there will be a new release.

Happy PostSharping!

-gael

I am happy to announce the release of PostSharp 2.0 CTP 3, available for download today.

This is principally a bug fixing release, since more than 40 issues have been solved. The most significant improvement is the Customer Experience Improvement Program (CEIP): the feature, fully opt-in, is able to automatically report unhandled exceptions in PostSharp, and collects some anonymous usage statistics. The CEIP has been included in an intermediate build between CTP 2 and CTP 3, and most isRead More...

There’s ton of documentation out there on how to use Mercurial and its various clients. For this blog post, you’ll see me use a popular client called TortoiseHg. (Hg is the chemical element symbol for Mercury, hence Tortoise ”Hg” in case you’re wondering.) If you’re already familiar with TortoiseSVN, this will be very straight forward. 

Step 1:  Install TortoiseHg

You can install TortoiseHg from http://tortoisehg.bitbucket.org. Note: TortoiseHg is an extension of the Windows Explorer shell, so there is no application to launch.

When prompted for your personal information, the username you specify will not be associated with your CodePlex account. This username is only used for your local commits. We advise you to put in the same username as your Codeplex username.

Step 2: Create a new CodePlex project

In the Create a Project wizard, select Mercurial for Source Control.

Step 3: Clone the repository

Now you’ll want to create a local clone of the repository. You must do this step; otherwise, you cannot push code (i.e. check-in) to CodePlex.

First, create a new folder on your local machine where you want to download (or clone) the repository.

Next, use TortoiseHg to clone the repository in the newly created folder, as shown in the illustration.

You’ll be prompted by TortoiseHg for the Source path. You’ll need to get this URL from CodePlex. Go to the project, click on the Source Code tab, and under Source Control Setup, click Mercurial. You’ll see a window appear with the Clone URL.

This is the URL to insert into TortoiseHg Source path, as shown in the below.

Press Clone.

Once the clone is completed, the dialog will close and you’ll see a green checkmark indicating this is sync’ed with the Mercurial project on CodePlex.

Now let’s look inside the folder containing the cloned repository. Since the repository is empty, there is only the .hg folder, which stores the Mercurial repository. DO NOT MODIFY THIS FOLDER unless you know exactly what you are doing.

Step 4: Add your files to your local repository

Now you can simply add your files to this folder. In this example, I only have one file that I’m going to add.

Now right-click to bring up the Windows Explorer context menu, and select HG Commit. The HG Commit command will commit to local repository.

In the HG Commit dialog, fill out the description of the commit. (again this is just for local repository).

Make sure to check to commit all files (or whatever files you want to commit), as illustrated in red below.

Press the Commit button, accept any warnings, and you’ll be prompted with a status/success window.

Step 5: Push to CodePlex

To push the code to CodePlex, you’ll need to open the HG Repository Explorer as seen on the Windows Explorer context menu.

On the menu, you’ll see the Push icon. Press this to start the push to CodePlex.

You will be prompted for your CodePlex credentials at this point. Once you have typed in your CodePlex username and password, you’ll see a success dialog.

Now you can go to your CodePlex project and view the source code tab.

What is Mercurial?

Mercurial is a distributed source control management system. For new projects created on CodePlex.com, you will be able to choose from either Team Foundation Server or Mercurial as your source control repository.

To illustrate, in the Create a Project wizard you’ll see the following:

If you are a current project owner and wish to switch to Mercurial, please contact us at CodePlex Support with your project name, and we’ll be glad to help you out.

Why DVCS?

Adding distributed version control support to CodePlex has become a top feature request from users, as the popularity of DVCS for open source development has grown significantly. Mercurial is one of the most popular distributed version control systems and offers great support for Windows based tools as well as works very well as a hosted service.

If you are new to Distributed Source Control Systems, please read this section!

Mercurial is a Distributed Version Control System (DVCS). Unlike Team Foundation Server, DVCS has a very different model for collaborating on an open source project.

• In DVCS, you do not check in and out changes. You check in and out the entire set of changes (aka the repository).

To get started, you first make a local copy of the repository, or clone the repository. In TFS speak, this is the equivalent of getting the entire history (source code + metadata) of each and every change set in source control. It is literally making a copy of everything you see in the CodePlex source control. Since you are copying the entire repository, there isn’t a notion of “checking out”.

• In DVCS, you commit to the local repository, and push your changes back to CodePlex.

Since you have your own repository, you “check in” by committing to your local repository. Once you’ve committed locally, you can “check in” those changes back to CodePlex by pushing those changes. Hence the term “check in” doesn’t apply because it is overloaded in the DVCS context.

A quick recap:

• Anyone can clone. (Create local repository, Get all change sets from repository)
• Anyone can commit. (Check-in to their local repository)
• Anyone can pull. (Get all change sets from repository)
• Only team can push. (check-in of local repository to CodePlex)

See our post Using Mercurial on CodePlex for a step-by-step walkthrough.

We have just released Mono 2.4.3.1, a bug fix release for the Mono 2.4.x series. The Mono 2.4.3.1 Release Notes include the full details on new features and bug fixes.

Mono 2.4.3.1 can be downloaded from our download page.

We have just released Mono 2.6.1, a bug fix release for the Mono 2.6.x series. The Mono 2.6.1 Release Notes include the full details on new features and bug fixes.

Mono 2.6.1 can be downloaded from our download page.

We have released Moonlight 2 an open source implementation of Silverlight 2 for Linux (with some extra added features).

Read Miguel's blog for more details.

Today we are releasing the much anticipated upgrades to both. Mono 2.6 and MonoDevelop 2.2.

For those in a hurry, binaries and source are available from:

• Mono Download page.
• MonoDevelop Download page.

And if you want a quick mnemonic to remember this release, just think debugger! and cross platform.

The Mono team and contributors worked on this release like we have never worked before. Thanks to everyone that reported bugs, filed feature requests, contributed code and helped newcomers with Mono.

Mono 2.6 highlights:

• WCF client and server, the subset exposed by Silverlight 2.0.
• LLVM support, to improve performance on server/computational loads.
• Continuations/Co-routine framework Mono.Tasklets (background info)
• LINQ to SQL using DbLinq.
• New Soft Debugger, integrated with MonoDevelop on Unix and OSX (background).
• System.IO.Packaging.
• csharp shell now supports auto-completion (press tab to complete)
• xbuild can now build most msbuild projects.
• Mono debuts a verifier and security sandbox (used by Moonlight).
• More complete 3.5 API coverage.
• This release includes Microsoft's open sourced ASP.NET MVC, ASP.NET AJAX and Microsoft's Dynamic Language Runtime.
• Faster and slimmer.

MonoDevelop 2.2 highlights (screenshots here and here):

• MonoDevelop code is now LGPLv2 and MIT X11 licensed. We have removed all of the GPL code, allowing addins to use Apache, MS-PL code as well as allowing proprietary add-ins to be used with MonoDevelop (like RemObject's Oxygene).
• User interface improvements: the first thing that MonoDevelop users will notice is that we have upgraded the UI to fit modern ideas. We borrowed ideas from Chrome, Firefox, Visual Studio, Eclipse and XCode.
• ASP.NET MVC support, you can now develop, debug and build ASP.NET MVC applications from MonoDevelop.
• New T4 Macro processor (Text Template Transformation Toolkit) integrated directly into the IDE (Mono's T4 is also available as a reusable library for use and abuse in your own programs).
• Moonlight Project Support: you can now build, debug and run Moonlight applications using MonoDevelop.
• New MacOS and Windows support. Check our feature matrix for details.
• New Debugger support allows debugging Console, Gtk#, ASP.NET, iPhone and Moonlight applications.
• Extensive text editor improvements:
  • Dynamic abbrev (Just like Emacs' Alt-/)
  • Code generator (Alt-Insert)
  • Acronym matching
  • Code templates
  • Block selection
  • C# Formatter
• New refactoring commands:
  • Inline Rename (see screenshot).
  • Resolve Namespace
  • Rename Refactoring with Preview
  • Extract Method
  • Declare Local Variable
  • Integrate Temporary Variable
  • Introduce Constant
  • Move Type to Own File
  • Remove Unused Usings
  • Sort Usings
  • Create/Remove Backing Store
  • Keybindable Commands
• Python add-in has graduated to be a supported plugin, includes code completion, syntax checking, method and class locator and code folding.
• iPhone development plugin.

The team is on #mono, #monodev and #monodevelop on irc.gnome.org fielding any questions you might have.

We have just released Mono 2.4.3, a bug fix release for the Mono 2.4.xx series. The Mono 2.4.3 Release Notes include the full details on new features and bug fixes.

Mono 2.4.3 can be downloaded from our download page.

Tracing has long been the "Hello, world" sample of Aspect-Oriented Programming. PostSharp does not make exception: tracing is still the first aspect visible on the home page, and most of early PostSharp bloggers did demonstrate AOP on a tracing aspect.

Yet, as tracing is a fundamental part of any non-trivial application, some advanced tools are available to .NET developers. Two of them deserve a special attention since their vendor provides aspects that can be directly used with PostSharp: Gibraltar and SmartInspect.

Don't ask me to compare these toolkits: they are actually sharp competitors. Both have good web sites and a free trial, so I can only recommend you give them both a try! And both have identified PostSharp as a natural complement to their product (Gibraltar being the first).

Gibraltar

I have a special moral debt to Jay Cincotta, one of the guys behind Gibraltar, since he recorded an amazing webcast of using PostSharp and Gibraltar together. Jay, thank you very much for this video, I know how hard it is to produce!

With these aspects you can declaratively add Gibraltar logging to your programs by simply tagging whatever methods, classes or namespaces you wish. This lets you add powerful logging to your applications without the effort, complexity or clutter of writing procedural logging code.

• [GTrace] logs entry and exit from tagged methods including appropriate message indentation.
• [GTraceField] logs every change in value of a tagged field.
• [GException] logs exceptions at the point they are raised. This is a handy safe guard to ensure that both handled and unhandled exceptions are logged by Gibraltar.
• [GTimer] lets you graph method execution time in Gibraltar providing invaluable information to identify bottlenecks and optimize performance.

These aspects (not the toolkit itself) are open-source and are hosted on Google Code at http://code.google.com/p/postsharp-user-plugins/.

For more information, see Using PostSharp with Gibraltar on their web site.

SmartInspect

Following Gibraltar, SmartInspect provides similar aspects:

• [SiTrace] automatically generates two log messages for each method call: one for entering a method and one when a method exits. You can also log the passed method arguments (when entering a method) and the method result (when exiting a method), respectively.
• [SiException] records all exceptions occurring in methods enhanced by the aspect.
• [SiField] lets you automatically record any changes to values of object or class fields.

The aspects can be downloaded from SmartInspect Resources & Extras (look for SmartInspect PostSharp Adapter).

For more information, see Aspect-oriented logging for .NET with PostSharp and SmartInspect on their web site.

Support for Other Logging Frameworks

If you're interested in using PostSharp with Log4Net, remember to check out Log4PostSharp, a project of Michal Dabrowski and Mark Kharitonov. Note that, contrarily to what's now offered by Gibraltar and SmartInspect, Log4PostSharp directly emits optimal instructions, resulting in much better runtime performance. This is not a feature of the logging framework but of the aspect implementation.

Interestingly, there is also some aging project from Eclipse, Build to Manage for .NET, providing PostSharp aspects for the IBM Tivoli platform.

PostSharp Emerged as the De-Facto Standard

What's happening there is that PostSharp is emerging as the de-facto standard for aspect-oriented programming on Microsoft .NET, just like AspectJ is for Java.

PostSharp 2.0 has been designed for the multi-vendor scenario, so that multiple aspects shall merge robustly when applied on the same element of code, even if these aspects come from different vendors who don't know about each other.

This means that ISVs can confidently rely on PostSharp to deliver aspects to their own customers. Good to know: the upcoming price structure shall make it very affordable for small ISVs to redistribute PostSharp free of royalties -- while enabling their own customers to use all professional features of PostSharp 2.0, including the IDE extension, in conjunction with their software.

Happy PostSharping!

-gael

 

Tracing has long been the "Hello, world" sample of Aspect-Oriented
Programming. PostSharp does not make exception: tracing is still the first
aspect visible on the home page, and most of early PostSharp bloggers did
demonstrate AOP on a tracing aspect.

Yet, as tracing is a fundamental part of any non-trivial application, some
advanced tools are available to .NET developers. Two of them deserve a special
attention since their vendor provides aspects that can be directly used with Read More...

I am pleased to announce PostSharp 2.0 CTP 2, available for download today.

Additionally to uncountable bug fixes, this new CTP brings the following features:

• Support for .NET 4.0;
• Support for Microsoft Visual Studio 2010 (including the IDE extension);
• Support for Mono 2.4.

This release is hardcoded to expire on February 1st, 2010. It is not possible to purchase a license yet.

The following features are not included in CTP 2 but are planned for a future preview of 2.0:

• Conceptual Documentation;
• Reference Documentation and Conceptual Documentation of PostSharp SDK (previously PostSharp Core);
• Support for Silverlight and Compact Framework.

Continue good work submitting feedback on PostSharp forum and issue tracker.

Happy PostSharping!

-gael

I am pleased to announce PostSharp 2.0 CTP 2, available for
download
today.

Additionally to uncountable bug fixes, this new CTP brings the following
features:

Support for .NET 4.0;
Support for Microsoft Visual Studio 2010 (including the IDE extension);
Support for Mono 2.4.

This release is hardcoded to expire on February 1st, 2010. It is not possible
to purchase a license yet.

The following features are not included in CTP 2 but are planned for
a future preview of Read More...

I'll present PostSharp and Aspect-Oriented Programming at MS Fest 2009, taking place in Prague, Czech Republic, this week-end (November 28th and 29th), and organized by students of the Math-Phys Institute of the Charles University.

My presentation will be in Czech -- I'm getting used to be the only one not to make the show in his mother tongue (mine is French)...

There will be a lot of fun! I gave the same presentation in Munich, Germany last month, and it was considered an homage to Mr Bean! No, seriously guys, AOP is serious stuff!

-gael