New Module for FogBugz @ Time Management System

Time Management System

We have just built a new time management system for vanguard software group, that integrates seemlessly with fogbugz.

FogBugz is the world’s easiest bug tracking system, built for teams who are serious about shipping great software.

The effort was put to make time spent on case report easy for developers/ managers to report. Which will in turn help management see where we the load and how we can make it more happy place to work. With this simple goal, we developed and we are going to reep its benefits soon.

Technologies Used:

  • C#
  • Ajax
  • JQuery
  • HTML
  • jQGrid


NOTE: FogBugz is trademark of “Fog Creek Software”

“Revert To Parent” Option at IIS, The requested content appears to be script and will not be served by the static file handler.

Lately, i h ad changed my local deployment method for webservices that are used during development.

I am directly publishing the web service to iis folder, BUT got stuck with problem that it wont run and give me following error

HTTP Error 404.17 – Not Found

The requested content appears to be script and will not be served by the static file handler.

Now,  everything seemed to be in place but it was handler mapping settings that somehow got lost for the site.

So i used “Revert to Parent” within handler mapping icon under website’s feature view in IIS7.

I hope this helps out some folks.


JOB: Require Senior Asp.NET Developers x 2


We are require another Developer at Vanguard Software Group for their pakistan office.

Experience Required: 4+

Number of Post: 2 now …

What we offer:

  1. Smooth Enviornment
  2. Good work ethics
  3. Laptop
  4. Medical
  5. Paid Leaves
  6. Opportunity to learn new things
  7. No LATE SITTINGS 🙂 – Guaranteed

So, send in your Cvs to /


Looking forward for good ones…




JOB: Require Senior Software Engineers at Vanguard Software Group (Lahore, Pakistan)

Number of Posts
    3 (Three)


Main Objectives
Vanguard Software Group requires highly talented and experienced ASP.NET resources to join highly technical team.

Should have Experience In
• 3.5
• 4.0
• C#
• SQL Server
• Microsoft Ajax
• JQuery
• Web Services – SOAP
• WCF (nice to have)

• Strong knowledge of SDLC and RAD Model.
• 5+ years of development experience in Microsoft .NET framework, ASP.NET(C#) and infragistics tools.
• Must be a good Database engineer who can work with or develop SQL queries and stored procedures for complex scenarios.
• Ability to multi-task in a fast paced, changing environment.
• Ability to achieve set goals and deadlines.
• Ability to self-motivate and self-direct.
• Demonstrate excellent analytical and problem solving skills.
• Demonstrate excellent communication and interpersonal skills.
• Must have good analytical skills.
• Good grasp over object oriented concepts.


• Medical Allowance
• Handsome Salary
• Lap Top

Send your resumes to

Uniqueness of Browser Instance

We @ Vanguard Software Group and also many other places we came across situations where we needed to somehow uniquely identify the browser instance of the user working with site (the concept applies to any web technology – asp, php, cold fusion …).


1- Session behaviour when you are working with In Process & with State Server. In earlier mode the application events for session end and start work fine, but still not when user closes the browser.

2- In case of State Server mode the session application events done even get fired, so we are at loss to how to track somebody who is no longer using our site.


The solution is simple one, to get RID of the session default implementation all-together :)… May of you will be surprised to hear it. But anyways,

Here is the idea (which we actually implemented in full blown manner)

When you’re working with web applications, your applications do have a start page. That start page can be used to generate a unique token for that particualr instance of the browser, and with each request to following append that token to Query strings for any more pages you visit while getting your user navigate through different areas of the websites.


When user requests your site, it goes to default.aspx (or whatever default you set) – Now generate GUID and store it within the ViewState of the page.

Now when user logs in – just pass that stored GUID to next page as Parameter. it will be something like GUID here]

Now, at this point that “Guid” is the unique token that you need to have for storing any information that you need for that logged in user.

Now, you will be thinking if we are not using session than where to store this information?

There can be more than one ways you could do that:

1-      Use Cache

2-      Use Distributed Cache (for Webfarm/ webgarden deployments)

For first option of “Cache”, just put in the Guid prefix with each key you put in, just like

Cache.Add( Request[“”Guid] + “Key”, “Value”)

Now, above is pretty straight forward – you can enhance it more to work wonders for you. Another you could do that, you can add timespan for the cached object so it does not lives in there for application life cycle or whatever default value is.

For Second option for Distributed cache you can use following

1-      NCache

2-      Microsoft Project named “Velocity”

Being Microsoft guy, I would like to use Velocity which is growing quite rapidly and quite fast as well. You search for “Velocity” and you will find bundle of articles on how to use it.

But to use this option – beware that you need to measure your project size and deployment strategy, as it requires Power Shell commands to work it out.


Generate Unique token for first request from a user to your application, and use that token until user logs off or closes the browser. When user opens new one that GUID gets created again, and there is no way that two brwoser instances would share that same guid. if you go this path options are unlimited. You apply this thought on cookie names etc …

Thanks, Caching & Scalibility

Today, we ran across the requirement of using Cache in our web garden/ farm enabled product called LoanVantage. Though we already knew that it would not work under current default implementation of caching in, but it seemed we had little choice of what to use or not. 

So, suddenly GOOGLING suggested us to a name “Velocity” for caching… and it was none other than Microsoft’s Solution, though in CTP but it was something to look on. So digging in more deeply downloaded this from 

With help of little code in samples – we were rocking in one hour and were ready to test our application with all this stuff. Though its in CTP, but quite useful – some enhancements would be needed to make it work beautifully.

 You can find more details on