<2006 June>
SunMonTueWedThuFriSat
28293031123
45678910
11121314151617
18192021222324
2526272829301
2345678

On this page...

Search

Links

Member of...


ASP Insiders

MVP Visual Developer ASP/ASP.NET

Enter CodeZone

Blog Categories

Microsoft

Blogroll

Deutsche Resourcen

Management

Sign In
 

#  Tuesday, 20 June 2006

Now, that scalability documents list is way cool. A lot good stuff on IIS performance, and especially real-world debugging of Web applications.

Categories: IIS
Tuesday, 20 June 2006 14:12:04 (W. Europe Daylight Time, UTC+02:00)  #    Comments [0]

 

The blog post ADO.NET vNext: The Entity Framework, LINQ and more on the Data Access Blog has links to all relevant articles on the next version of ADO.NET and the Entity Data Model (EDM). Make sure to read at least the vision document.

Categories: .NET
Tuesday, 20 June 2006 14:06:47 (W. Europe Daylight Time, UTC+02:00)  #    Comments [0]

 

As promised, here is the list of links / articles / samples that I used for preparing my talk "Build Provider in ASP.NET 2.0":

Hope you will find those useful.

Categories: 2 Ohhhh | ASP.NET | this | Training and Conferences
Tuesday, 20 June 2006 13:14:32 (W. Europe Daylight Time, UTC+02:00)  #    Comments [0]

 



#  Monday, 19 June 2006

Half an hour ago, I completed my talk "Windows Workflow Foundation & ASP.NET 2.0". As promised, here is the list of links to sites / documents that I used to prepare this talk & accompanying samples.

Also, see my last post on ASP.NET PageFlow CTP. This was the last part on "future technologies".

Update A foto from my talk on Monday (debugging a workflow in ASP.NET):

Monday, 19 June 2006 11:39:07 (W. Europe Daylight Time, UTC+02:00)  #    Comments [1]

 



#  Tuesday, 13 June 2006

Yesterday night, I watched a WebCast from TechEd Boston - "An Overview of ASP.NET and Windows Workflow Foundation". What this innocuous title hid was the fact that Kashif Alam (PM in the Developer Division) was presenting vNext features for ASP.NET workflow integration: Page flow (PageFlow) as well as UI flow (UIFlow), plus the accompanying extensibility model.

What do those two separate approaches provide? Well, you get MVC (model-view-controller) support for same-page (UIFlow) as well as cross-page (PageFlow) scenarios. Pretty neat was the included "Choosing the right solution" slide to get an idea what's in store:

Task <asp:wizard...> PageFlow UIFlow
Single page x x
Multiple pages x
State when close browser x x
Integrate with Enterprise WF x x
Client support x x
Built-in navigation UI x
Extensibility to other controllers x x

As developers, we will get our hands on this later this year in the form of the "ASP.NET PageFlow CTP" (at least that's the current name), and it will be deployed with Orcas.

Categories: .NET | ASP.NET | Tri 0 | Workflow Foundation
Tuesday, 13 June 2006 08:28:38 (W. Europe Daylight Time, UTC+02:00)  #    Comments [0]

 

NetFx3 is the new community site that focuses on the four .Net Framework 3.0 technologies Windows Communication Foundation, Windows Presentation Foundation, Windows Workflow Foundation and Windows CardSpace.

Categories: .NET | Tri 0
Tuesday, 13 June 2006 00:03:11 (W. Europe Daylight Time, UTC+02:00)  #    Comments [0]

 



#  Saturday, 10 June 2006

In less than ten days, this year's ASP Konferenz will take place in Burghausen, Germany. This time, I will be presenting four topics: Windows Workflow Foundation & ASP.NET 2.0, Build Providers in ASP.NET 2.0, IIS 6.0 & ASP.NET 2.0 Secure Deployment and finally Health Monitoring in ASP.NET 2.0.

Saturday, 10 June 2006 08:46:17 (W. Europe Daylight Time, UTC+02:00)  #    Comments [0]

 



#  Friday, 09 June 2006

When working with a team, it is always a good idea to have dependencies in a separate folder so everyone can reference them using relative paths:

References from this dependencies folder then look as follows in the MyWinApp.csproj file:

  <ItemGroup>
    <Reference Include="Boo.Lang, Version=1.0.0.0, ...">
      <SpecificVersion>False</SpecificVersion>
      <HintPath>..\Dependencies\\Boo.Lang.dll</HintPath>
    </Reference>
...
    <Reference Include="System" />
...
    <Reference Include="System.Xml" />
  </ItemGroup>

So every team member that checks out the project will be able to work in their workspace, as well as the build server will have all the proper references. Great.

But what about the following scenario: depending on Release or Debug, you need different references - how can you solve this problem? The first step is to go and create a directory for each configuration below the Dependencies folder:

Next, copy the assemblies to the respective directories. Plus, you have to modify the .csproj file and add $(Configuration) to the external reference's hint path:

  <ItemGroup>
    <Reference Include="Boo.Lang, Version=1.0.0.0, ...">
      <SpecificVersion>False</SpecificVersion>
      <HintPath>..\Dependencies\$(Configuration)\\Boo.Lang.dll</HintPath>
    </Reference>

That's it - even Visual Studio will honor this change and still provide you with IntelliSense.

Before closing, I want to mention a new tool - even though it doesn't (yet) support editing the hint path, you should check out Attrice's Microsoft Build Sidekick. It allows you to graphically edit .*proj files:

Categories: .NET | Cool Download | Visual Studio
Friday, 09 June 2006 08:07:18 (W. Europe Daylight Time, UTC+02:00)  #    Comments [0]

 



#  Monday, 05 June 2006

Disclaimer: I am the Senior Project Wrangler for #develop. Therefore I am biased as well as knowledgeable.

Today, we shipped RC2 of SharpDevelop2. For those of you who haven't heard of it before, it is an Integrated Development Environment (IDE) for .NET. I will get to the features in just a second. First, I want to thank all developers that spent time on making v2 a reality. Daniel, the lead developer on v2, actually implemented a nice little tool for showing the project statistics, you can read more and download the utility in his blog Analyzing the code in SharpDevelop. Wow, we started quite a long ago on this baby.

I promised to get back to the feature set. Let's tackle it with more than a grain of blog posts and feature videos:

Supported Programming Languages

My definition of support is as follows: full code completion (aka IntelliSense) and a working Windows forms designer. Therefore, three languages qualify: C#, VB.NET and Boo. Aside from those fully supported languages, you get syntax highlighting for many more.

Speaking of syntax highlighting and code completion: both features are supported for XML files. You can check it out in the xml editing experience feature video (yes, this is available since v1.1!) You get this for MSBuild files too!

Features You Would Expect

Let's start with the integrated debugger. This has been our achilles heel since the very beginning, as implementing a debugger isn't exactly a piece of cake. However, thanks to David, v2 sports a debugger and you can watch a demo.

Let's continue with a simple list: Search & Replace, code folding, code templates (just try Ctrl+J in the editor), a toolbox and more.

Cool Features

Ahhh. At last. Let's see what we got:

  • Unit testing (since 1.1, NUnit-based)
  • Code Coverage (2.0, based on NCover - read more in Matt's blog post)
  • Documentation generation (since 1.1, based on NDoc)
  • Quick XML Doc (since 1.1, just try Ctrl+Q to get a preview of the HTML help that will be generated for your XML comments)
  • Auto code generation (since 1.1, just try Alt+Ins)
  • Code converter - convert your projects from C# to VB.NET and vice versa (since 1.1). New in 2.0: three way with Boo.
  • Reports. Yes, SharpDevelop ships with a free-to-use report engine, #report. It was added late in 1.x, now improved for 2.0. Watch the demo
  • Support for multiple frameworks - although 2.0 is the default, SharpDevelop can target 1.1 as well as Mono. Even Gtk# is supported.
  • Ctrl+Mousewheel zooming. You will like it. I do.

What's Not There

We ain't a big software company, so we have to tackle features in order. Therefore, you won't find ASP.NET support in SharpDevelop, as well as others: CF support (planned for 2.1), version control (planned for 2.1), ClickOnce (planned for 2.1)...

Even if you don't plan on using SharpDevelop for your daily work, give it a try and let us know what you like and what not on our forums. You might even learn about a cool new feature like Component Inspector that is coming with 2.1, code-named Serralongue. And we'd be more than happy to welcome additional developers, testers, writers and translators.

Categories: .NET | Cool Download | this | Use the source Luke
Monday, 05 June 2006 23:29:57 (W. Europe Daylight Time, UTC+02:00)  #    Comments [0]

 

The concept of shelving was made popular by Visual Studio Team System's source control system - it allows you to "shelve" your changes for a couple reasons, like:

  • You have to work on a bug fix immediately, but you are in the middle of implementing a new feature. You cannot check in those half-baked changes, only the bug fix. So you shelve your feature work. Once done with the bug fix, you unshelve the feature work and continue.
  • Sharing work. Another developer needs the changes you are currently working on, but you are not yet done. So you shelve your changes and the other dev unshelves them and can get productive immediately.
  • Code review. Instead of having someone come over to your office (or worse, email the files) to review the changes before checkin, you shelve them and the reviewer can unshelve them.
  • Backup. How many times do you leave your workplace with a feature not yet completed? What to do with this build-breaking half-baked work? Shelve it!

Now you get the idea why shelving is pretty neat. Even Subversion does support the concept although it is not explicitly there: the blog posts Shelving in Subversion and Shelving Subversion show how you can make shelving happen with Subversion.

Categories: Subversion | Team System
Monday, 05 June 2006 11:49:37 (W. Europe Daylight Time, UTC+02:00)  #    Comments [0]

 



© Copyright 2017 Christoph Wille

newtelligence dasBlog 2.3.9074.18820
Subscribe to this weblog's RSS feed with SharpReader, Radio Userland, NewsGator or any other aggregator listening on port 5335 by clicking this button.   RSS 2.0|Atom 1.0  Send mail to the author(s)

 
Don't contact us via this (fleischfalle@alphasierrapapa.com) email address.