October 2005 - Posts
SQL Server 2005, Visual Studio 2005, BizTalk 2006 Launch Tour
Will you be attending the Vancouver date for the Launch Tour? I have been invited to take part in the Cabana, or formally known as "Ask the Experts" booth. Someone seems to think I'm an "expert". ;) Be sure to drop by!
I was given the OK to bring some of my own marketing materials for my own event which I plan on holding in Vancouver in March why dont you drop by the Cabana and find out what that is!?
Launch2005
For some reason when I try to load up the secure MSDN subscriber page I get the following page:
I recall that MSFT told us there is a new URL that is in place now and to make the switch, but you get into the habit of going to a single URL for what you need and it is hard to break it. Here is the good/new URL which works for me.
Since the guy beside me doesnt see it, and my machine at home on another completely different network does not see it either it could be a DNS issue. I flushed my local DNS (ipconfig /flushdns) and it seemed to have fixed it. -Temporarily-. I just waited for about 1 minute and its back to its misbehaving. I see the same page as above again.
The Worlds Best App
Its a contest put on by Microsoft based on their MSN Messenger product.
Stolen from the site:
"Use our free Software Development Kit to create your masterpiece with MSN Messenger Activity API. You can make just about anything, be it an innovative business tool, clever communication gizmo or a great new game."
I started to go through their API and found that they are missing the basic "Hello World" or bare bones setup. I decided to quickly throw this together.
First off, get the SDK and get my BareBones Sample.
And finally:
1. Copy barebones.html to some place on your web root (localhost is fine)
2. Edit MSGRP2P.xml and point the URL tag to that HTTP location
3. Copy MSGRP2P.xml file to: C:\Program Files\MSN Messenger\
4. Double click any contact
5. Go to the "Actions" menu, you should see "Start Bare Bones"
6. The page should load up on the right side
Fairly simple setup. If you open up instructions.txt I stuff it full of a bunch of notes which I found quite useful.
Happy Coding!
For safe keeping I'm posting up my Tortoise exclusion list
tmp pkg bin cvs Release Debug release debug obj TempPE temp _private _vti_bin _vti_cnf _vti_log _vti_pvt _vti_script _vti_txt thumbs.db *.obj *.ncb *.lib *.idb *.pdb *.ilk *.msi *.res *.pch *.suo *.aps *.*~ *.~* ~*.* *.user *-results.xml *.mdb *.ldb *.incr *.scc *.SCC *.vspscc *.projdata *.resources *.vbw ~vssc Build doc
This just got pointed out to me this morning.
I did the poll as well and as of right now 4.7% of the people who voted agree with the author; 51.5% believe it is up to the Vendor. Duh!
Why on earth someone would want to place so much responsibility on a developer is beyond me. Personally I would rather think it is the solution/security architects' role to handle the end to end security of an application, and ultimately the management of that organization. Management has to ensure that their product meets their expectations and needs including details such as these. It is up to them to put the methods and processes in place to ensure that these concerns defined and are met otherwise you will get stupid mistakes like the one mentioned in the article.
Failing to Plan is like Planning to Fail.
I made MVP again this year!
So you want to debug some Javascript?
There are two solutions that you can currently use, the first integrates nicely into VS.NET and IE and the second into Firefox.
The IE Solution:
IE and VS.NET both ship with nice javascript debugging support; here is the simple steps to get it to work:
1. Turn off "Disable script debugging". In IE go to Tools, Options, Avanced Tab and in the "Browsing" section make sure that "Disable script debugging" is NOT checked. Accept that change.
2. Open up VS.NET into your favorite solution, which of course includes some javascript markup.
3. Run the solution.
4. Once the project is ran, and the IE window is open jump back over to VS.NET.
5. Under the Debug menu, Windows, choose Running Documents. This should show a window on the right side with a list of the running documents. It should show the aspx page any any .js files you have included. Open up any of the .JS files and set breakpoints in your code. Once the script is executed it should stop at your breakpoints and give you all the current watch funcationality that you have come to expect from VS.NET.
The Firefox solution:
Mozilla has a project named "Venkman" just for debugging.
Here is what I did in order to get this to work:
1. Install the extension from http://www.hacksrus.com/~ginda/venkman/. Note: In order to get Firefox to actually install this you need to add the "hacksrus.com" to your trusted sites. I dont trust this guy so what I did was right click the XPI and saved it to my desktop. From there you can click and drag it into a Firefox window which it will then install it. Also, remember that an XPI is just a zip file with a bunch of content. Feel free to rename the .XPI file to a .ZIP and take a peek whats inside.
2. Once you have the extension installed you will need to recycle the browser, do so now.
3. Open up the Javascript debugger. It can be found under Tools, Javascript debugger.
4. Open up the page you need to debug and set a breakpoint wherever you like. It also supports things like stepping over, into and out.
Resources:
Debug JavaScript in ASP.NET Apps
Venkman Homepage
Venkman Extension Installer page
Learning the Javascript debugger Venkman (an awesome usage guide)
Venkman FAQ
More Posts