Standing on the shoulders of giants. RSS 2.0
# Thursday, February 22, 2007

Passed the 70-554 exam today, now I'm officially a Microsoft Certified Professional Developer : Enterprise Application Developer.

This means I currently have the following certifications:

MCTS (Web, Win and Distributed), MCPD( Enterprise Application Developer), MCBDA (on Sql 2000), MCSD & MCAD

 

Thursday, February 22, 2007 3:48:33 PM (W. Europe Standard Time, UTC+01:00)  #    Comments [0] - Trackback
Certifications
# Saturday, February 17, 2007

Again for 2007-2008 Tam Tam had received the Microsoft Gold Partner status.

Saturday, February 17, 2007 3:07:15 PM (W. Europe Standard Time, UTC+01:00)  #    Comments [0] - Trackback
General
# Saturday, January 27, 2007

After passing the 70-553 upgrade exam, I am now a Microsoft Certified windows and web application Technology Specialist.

Next up the 70-554 exam to become a Microsoft Certified Professional Developer : Enterprise Application Developer.

 Update: Great reources for both the 70-553 and 70-554 exams.

Saturday, January 27, 2007 3:40:37 PM (W. Europe Standard Time, UTC+01:00)  #    Comments [0] - Trackback
Certifications
# Sunday, January 07, 2007

And we have an UI.

BlogML import screen

The BlogML import/export functionality for dasBlog is planned for a future release, but as soon as the project has officially moved to Asp.Net 2.0 it will be available in svn and the dailybuilds.

What features do you want for the import and export functionality? Currently it's an all or nothing operation, but things like selecting a date range for the export could be useful. And other suggestions?

Sunday, January 07, 2007 9:38:35 PM (W. Europe Standard Time, UTC+01:00)  #    Comments [0] - Trackback
BlogML | dasBlog
# Friday, January 05, 2007

public class A {
    public virtual void AA(){}
}

public abstract class B : A{
    public abstract override void AA();
}


If you now would define a class C : B, then C must implement the method AA again.
Friday, January 05, 2007 11:23:52 AM (W. Europe Standard Time, UTC+01:00)  #    Comments [0] - Trackback
Codesnippet | C#
# Sunday, December 31, 2006

This is a short walkthrough on how to get the REST and POX sample from the Vista SDK to work on IIS. I assume VS 2005 with SP 1 and IIS 5.1, but the changes required on IIS 6 are the same.

Before we begin make sure you have .Net 3.0 installed and either the Vista SDK or the WCF Samples. And IIS, with the mappings for Asp.Net and WCF.

The sample we'll modify to work with IIS is located in "TechnologySamples\Scenario\PoxMessaging\CS" directory. And since there are no code changes the VB sample should work too.

First load the solution and make sure the it actually compiles and works, so we have a known base system we can work from. Do this by first starting the server and next the client, if you don't get any un-handled exceptions, then everything works, so we're good to go.

Next create a new Web Application Project, names ServiceHost in the solution and make sure it uses IIS for hosting in the Properties Web tab.

Remove all files VS created in your new project, except for the web.config and copy all files from the service project, except for program.cs and app.config. Finally add a reference to the System.Runtime.Serialization and the System.ServiceModel assemblies. Now the project should compile, but won't do anything interesting.

To register the endpoint, we have to copy the serviceModel configuration from the app.config in the service project to the web.config. So add the following to the web.config file:

 










contract="Microsoft.ServiceModel.Samples.IUniversalContract" />


This is the same as the config in the app.config, with the baseAddresses node removed, since those are supplied by IIS.

Now add a new file to the web project named: "customers.svc" with the following content:

<%@ ServiceHost Language="C#" debug="true" service="Microsoft.ServiceModel.Samples.CustomerService" %>

Save all files and if you surf to http://localhost/servicehost/customers.svc/customers/1 , you should see the following:

http://tempuri.org/Customer" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">

100 Main Street

Bob

Do note how the "/customers" part maps to the endpoint you specified in the web.config and the "/1" to the id of the customer. If you leave off the "/1" you should get a list of customers.

Which indicates the GET HttpMethod is working, to get the other methods working, we have to make some changes to the IIS configuration. In the properties of the ServiceHost virtual directory in IIS, click the Configuration button.

 

Now find the .svc mapping in the Application Mappings, click Edit and select "All Verbs".

That's all there is to it. To test it you'll need to make some changes to the client project, to make sure it uses the correct URLs to access the service. See the attached solution for details.

 POX-REST-IIS-Sample.zip (11.69 KB)

Sunday, December 31, 2006 12:51:43 AM (W. Europe Standard Time, UTC+01:00)  #    Comments [0] - Trackback
C# | Services
# Wednesday, December 27, 2006

 ... or why does your tool introduce bugs in my code and doesn't warn me?

When migrating an ASP.NET 1.1 project to 2.0, using the VS 2005 (SP1) conversion wizard and the Web Application Project conversion tool (included in service pack 1), the AutoEventWireup @page attribute is set to "True" for all pages, even when you previously had set it to "False".

This potentially breaks your application, when you have eventhandlers for init/load/prerender bound manually in places where the conversion tool doesn't change them, e.g. in the constructor of a common basepage. This will cause the events to be handled twice, with unexpected results.

The problem is not that the default is changed from 1.1 to 2.0, but that by modifying my code the tool introduces new (interesting) bugs. And all this without a big neon-sign, which warns for the changes being made and the potential problems it introduces.

Wednesday, December 27, 2006 5:01:17 PM (W. Europe Standard Time, UTC+01:00)  #    Comments [0] - Trackback
ASP.NET

is an XML format for storing the contents of a blog; either for archival or migrating to a different blogging engine.

BlogML currently supports the following engines:

  • Community Server
  • Subtext
  • SingleUserBlog

And I finished a beta implementation for dasBlog today.

The current BlogML format does not support all the features dasBlog has, so the following information is lost when exporting your blog using BlogML:

  • Post specific languages; the language information for a post made in a different language than the default is lost;
  • Only trackbacks are exported; Pingbacks and referrals are lost; 
  • Attachments are not imported in this build;
  • Some properties of comments are lost (useragent, ip of user);

The current driver program is very basic, and requires some hacking to switch between import- and export-mode.

Note: although dasBlog is a .Net 1.1 project, this is written using .Net 2.0 as per the BlogML project.

download: dasblogml.zip

Wednesday, December 27, 2006 1:46:05 AM (W. Europe Standard Time, UTC+01:00)  #    Comments [1] - Trackback
BlogML | dasBlog
# Tuesday, December 26, 2006
Tuesday, December 26, 2006 3:25:32 PM (W. Europe Standard Time, UTC+01:00)  #    Comments [0] - Trackback
General | photo
About
© Copyright 2008
Paul van Brenk
Sign In
newtelligence dasBlog 2.3.8275.16006
All Content © 2008, Paul van Brenk
DasBlog theme 'Business' created by Christoph De Baene (delarou)