One of the big factors that drew us to move to Vermont in 1999 was the skiing. We can ski out our back door to the back country or drive 7 miles to our favorite lift-serve ski area: Mad River Glen.

But what is this?

I took this on Jan 21 out my front window

and this one I took 5 minutes ago

Congratulations to the Windows Live Local team on being selected for an Editors Choice Award by PC Magazine!!

I had to laugh when I saw the screen shot in the PC Mag article. One of the tags is for Ft. Green Park in Brooklyn. In a former life (my 20's) I lived 1/2 block from that park.

(add'l plug for the WLL team: Want to join this "winning team"? They are hiring!!)

Now here's a guy about whom I can literally say "I knew him when."

I knew Ken Levy when he was a wee lad (a teen) who had written the most popular add-in for professional FoxPro developers everywhere - GenScrnX!

This was so long ago that rather than an email, Ken used an ID of  76350,2610. Yep, Compuserve.

Ken, along with YAG, has been doing great things at Microsoft for a whole lotta years now. But now Ken is straying from the fold and got lured over to Windows Live.

Well, I'm quoting Scott Watermasysk on that, but since he and I talked about this frequently over the years while I was heavily involved with INETA, I'm happy to see this finally happen! Looks like newlywed Jason Beres has a hand in this, too. Excellent!

Hopefully, everyone gets the little joke in the upper right hand corner of the home page.

These guys are NOT to be missed if you are able to get to Waltham, MA on March 25th. It's a "mini-code camp." A one day one track event.

Patrick Hynds and Duane LaFlotte are two guys you want on YOUR side when it comes to hacking. Had Duane found a different mentor in his youth, he'd be the guy downloading all of your credit card companies most secure data! Phew, we lucked out.

Not only do they know amazing things about security, but they are one hell of an entertaining duo!

One word of advice though. If Patrick offers to drive you around Boston, do NOT, I repeat, do NOT sit in the back seat!

For as long as I've been using outlook, I have always clicked on the "new message" icon to create a message.

I just accidentally double clicked on a whitespace below my message list in unread mail (where I have a red circle and yes I did that with a mouse, not on a tablet) and voila!! A new email message window opened up. Man, this is going to help me be even lazier. I won't have to move the  mouse all the way up into that corner any more!

It works when you are at the bottom of any view that lists emails. Of course, most of my email folders are bottomless pits of endless emails, but at least the unread mail looks minimal when I have the groups closed.

Did you know that there are 40 command line utitiles in .NET? [read more ...]

[A DevLife post]

I saw this question in the newgroups and wanted to blog about it because it is a real gotcha that gotme too when I first started working with WSE 3.0.

If you set the WSE 3.0 diagnostics tab to output trace files, you can get a look at the messages going out of and coming into your client as well as going out of and coming into your webservice.

Tip #1 Remember to turn OFF this tracing when you send your client app or web service into production. Left to it's own devices, the trace files will grow and grow and grow and one day you will be wondering why your web service is acting so slowly. That's because of the effort of opening up a 60MB file to add some text to the bottom of it!

Tip #2 The default file names are TraceInput.webinfo and TraceOutput.webinfo. Those extensions suck because you can't open them up in anything easily. I always change them to TraceInput.webinfo.xml and TraceOutput.webinfo.xml. Then I can double click on them and open them up in something like I.E. or an even more intelligent angle bracket reader. (Note:Nathan (a tester on the WSE team) makes a good point about this. If you forget to do #1, then #2 could very easily expose some super critical data for hackers on your production server! So you might be better off without this particular little trick of mine.)

Tip #3: Reading the trace files, remember that there is more than the header and body of the message in there. There is also processing info. That means that in an output file, the first thing you will see is the unprocessed message. Your app has created the message, but it hasn't been through WSE yet to get all it's protection before it's sent out on the wire. This is very confusing and can even be a little frightening because if you have encrypted your message, the first thing you see is a message body with clear text! Notice,though, that it is surrounded by tags that say <processingStep description="Unprocessed Message">. Now at the bottom of that <outputMessage> and you will see the <processingStep description="Processed message">. That is the message that is going out on the wire and hopefully looks more like what you expected.

On the incoming message, the first thing in the door (again the Unprocessed Message) is what just came in off the wire. So that is the real soap message and should display all of the properties you expected - encryption and any thing else you demanded of the message. Then you can read through the processing steps and the last step has the fully processed message that is about to get passed to your application. All of the security goo is gone and you will see clear text again, even when the actual message was totally secured.

Tip #4: If you want to see only the soap that went over the wire, bag the built in tracing and use Mike Taulty's sweet little WSE 3.0 Tracing Tool.

Tip #5: For even more detailed inspection and diagnostics of your web service messages, check out Mindreef's SoapScope.

Three years ago I did a presentation at Vermont.NET on Architecting Applications with Web Services. (Proof is at the past events page - check Feb 2003!) 

I clearly remember the question of overloaded web methods coming up in that session. I didn't know the answer so I tried it right then and there and it didn't work. Someone mentioned there was a way to get around it and we found that solution another day.

It's still a question for a lot of people who are coming to Web Services as OO programmers (which Visual Studio lets us do) and that is because many are unfamiliar with the attributes that can be used for web services. Or they see them but have no idea what they are there for.

Thom Robbins recently had someone ask the same question and blogged how to use attributes to enable overloading when defining web methods in Visual Studio.NET.

Three years ago, it seemed like a good idea to me. I didn't really grokWeb Services. I was just using them as a means to an end and I knew OO programming, not messaging.

However, now my perception has changed and it's important to note (as Thom does (thanks Thom!)) that just because you can do it, doesn't mean it's a good thing. It's the OO way, for sure, but it just does not jibe with messaging and contracts and it does not conform to WSI Basic profile which demands unique names for operations (web methods). So if you have any intentions of going outside of .NET with your messaging, don't do it. A contract needs to be clearly defined and by providing overloads, that just blows the contract away.

If you are writing what the plumbers call "silo" apps, .NET all the way through and you are controlling the client and the service, there's no harm outside of the damage you are doing to your brain. Still, it's important for the WSDL that represents your web service identifies does not identify itself as conforming to WSI Basic profile. When you create a new web service in VS2005, by default, the service has attributes that claim to conform to the Basic Profile. Thom includes the caveat in there to set the services' conformance claims to "none".

Here's what a .Net web service class that shows what Conformance Claims  looks like. ConformsTo is the claim. Emit embeds the claim in the wsdl.

<WebServiceBinding(ConformsTo:=WsiProfiles.BasicProfile1_1, EmitConformanceClaims:=True)> _
<WebService()> _
Public Class ShowConformance
  <WebMethod> _
  Public Function HelloWorld() As String
   Return "Hello"
  End Function
End Class

If you look at the wsdl (eg http:\\localhost\myservice.asmx?wsdl) you can see that claim. Here is the appropriate section of the wsdl.

When you explicitly define that the service does NOT conform, there is no claim in the WSDL that says "I do not conform". In that case, no claim is made at all.

So by marking your service with

ConformsTo:=WsiProfiles.None

even if you have EmitConformanceClaims set to true, there will be no wsi:Claim in the wsdl.

If you forget to remove the conformance claims, you will get a big fat error message when you try to call the asmx.

Service 'Service' does not conform to WS-I Basic Profile v1.1. Please examine each of the normative statement violations below.

and the detail tells you:

To make service conformant please make sure that all web methods belonging to the same binding have unique names.

The more you start understanding these things today, the more prepared you will be for WCF.

I have a web service that I wrote for one of my smart client apps to check for one of three states of connectivity: no network, local network connection to web server, web connection to the web server.

So I ping the web service at the local i.p. The operation returns a mystical "hello world". If that times out, then I ping the service at the i.p. of the web server as it is exposed to the web via ISA Server. If that times out as well, then they are told (politely of course) that they are S.O.L. and need some type of network access to run these particular functions.

I have a client side assembly dedicated to this as well as the web service.

Now Visual Basic .NET 2.0 has My.Computer.Network.Ping to which you pass a URI and a timeout period. There is one small code benefit to me as I have to dynamically construct the web service URL and using the new method, I can just ping the i.p. and not care about a complete path to the web service. However, the Network.Ping method requires a bunch of permission that I don't need in order to hit the web service. So I think that for now, I'll leave it alone and wokr on other things for my migration.

Pondering about being a user of development tools vs. being an inventor of these same tools... [read more...]

[A DevLife post]

Well, it seems really official now. GE purchased Burlington based IDX in 2005 for $1.2 billion. Today I got an email from someone at IDX asking me to update his email address from @idx.com to @ge.com!

That's going to take some getting used to.

Writing a conclusion or summary at the end of an article is hard work. In addition to it being deflating after the fun of hashing over lots of ideas, you have to be careful to avoid cliches like "powerful features".

Do you even read that last paragraph of a technical article? Does it help you get closure or is it just a dangling preposition, so to speak?

As I begin deploying new apps at my client site,  we made a discovery that we were easily able to correct.

After installing a .NET 2.0 app that uses Crystal Reports, we were unable to run Crystal Reports from our .NET 1.1 applications. We got an error indicating that it could not find the CrystalReports.Engine assembly.

The short story is that reinstalling CR .NET 1.1 after CR.NET 2.0 fixes the problem.

For the more curious, I did a little more exploration. I uninstalled the CR for .NET 2.0 but whatever it had stomped on did not fix itself and the 1.1 reports still did not work.

Then I reinstalled 1.1 which worked again and then 2.0 on top of it which again broke 1.1. (Just verifying that this was the direct cause.)

Lastly, we installed CR.NET 1.1 after CR.NET 2.0 and then all of the reporting works fine.

Well, not quite Paris, but how about the beautiful locale of Nice France?

This year, DevConnections is expanding it's venues to Europe with it's first conference in Nice form April 24 - 27th.

Many of the speakers that you are used to seeing at DevConnections in the U.S. will be there.

I won't be there, but will be doing four sessions at DevConnections in Orlando April 2- 6th.

See you in Orlando!

There's a cool new .net 2.0 feature I didn't know about until I needed to do this a few days ago. If your application has FullTrust, you can use the System.Data.Sql.SqlDataSourceEnumerator to get a list of available SQL servers (2000 and 2005 only). The query returns a DataTable which you can just attach to a combobox or drop down list.

 Dim instance As SqlDataSourceEnumerator =      SqlDataSourceEnumerator.Instance
 Dim dt As DataTable = instance.GetDataSources()

Remember, though, this requires the assembly to have full trust. There is not a specific permission you can apply to use this otherwise.

I'm experimenting with a simple .NET 2.0 WinForms application and ClickOnce and still, as is my destiny, banging my head on the wall.

My latest frustration (while trying to use all of the built-in automated functionality) is trying to limit who has access to the downloads.

For a particular application, we only want it to run in-house on the intranet, yet our webserver is exposed to the www. Windows Authentication sounds like a good solution, but it doesn't work if you are trying to deploy requirements in addition to the main application.

If I have the IIS properites of the deployment site set to allow anonymous users, everything works peachy-keen. However if I use integrated authentication and no anonymous users, I'm going around in circles and getting "access denied" errors which are buried in a log file (not something I want my users to deal with). If I pre-install the prerequisites manually (.net 2.0, etc.),then I can install the application from the "launch" hyperlink.

I can't believe that I am still in this hole and trying to out-think the available tools to get what I want. Is it so unusual to not want the entire world to have access to my client's applications?

There is an msdn document called Server Configuration Issues in ClickOnce Deployments which addresses the authentication problem directly.

Server Authentication Issues

"The files could not be downloaded from http://<remoteserver>/<myapplication>/.  The remote server returned an error: (401) Unathorized."

But even after following the above recommendation (where I have turned off anonymous access and selected integrated authentication, and am then prompted to log in) I can't follow through a full setup with requisites and the application. I have already described the result above.

Now I have the choice between just figuring out my own solution to this (not using the automatically generated publish page and building my own asp.net page for downloading some things anonymously and some things securely) or continuing to google endlessly to see if anyone else has dealt with this seemingly commonplace scenario.

Sadly this is just a tiny little exe and this down-the-toilet-again-weekend is making me more worried about getting my big multi-layered app working with ClickOnce.

Update about 2 hours later: After venting (in this blog post ) I came up with a solution that is somewhat clunky but does the trick for now. I am modified the publish.htm in the following way:

1. For the .NET 2.0 requirement, I put a hyperlink to the Microsoft's .NET 2.0 x86 redistributable download page.
2. For the crystal reports .net 2.0 msi, I put a hyperlink to the msi on our web server.
3. I changed the Install button to point to myapp.application, instead of setup.exe. Setup.exe tries to install the requirements.
4. I wrote text for #1 and #2 to explain to the users how to determine if .NET 2.0 or crystal reports needs to be installed, how long it might take and that this only needs to be done once on their computer.

I also had to muck with proxies on the machines on the intranet. They get at the web through isa-server. So for the local link to publish.htm and the msi for crystal, everything was okay. With the isa-server proxy set up for non-local sites, the microsoft link was okay. But even with "don't use proxy for local urls", I couldn't get the myapp.application to install. Therefore, I had to explicitly put the ip address of intranet web-server into the exceptions list on the Advanced page for the proxy settings. What I'm talking about here is in Internet Explorer/ Tools / Internet Option / Connections / LAN Settings/ "Use a Proxy Server" with my proxy info and "By Pass Proxy Server for Local Addresses" are both checked. Then click on the Advanced button and add the ip of the local web server into "exceptions".

I have not tried this over the web yet, but remember, my goal is for intranet only installs on this application.

Don't Forget: www.acehaid.org