IIS to Sql Server Login Failed when not on same domain

Thats happened a few time already (over the past few years). IIS likes to know who you are before it lets you talk to SQL server. So a nice blog here if you are connecting to a Sql Server db from IIS and the two machines are not under the same AD domain.

http://beyondthispoint.blogspot.com/2006/04/setting-up-iis6-application-pool.html

Do the steps, it works! This post is like an extended book mark!

Can we get any more virtual ?

I am stuck with the virtualization question for a bit. To virtualize or not ? Have to.. its in the work I do. So here is a little list. Help me fix it, but I'll throw it in for a start:

I want to..	So ..
Develop on my Win XP/Vista/2003 machine or laptop.	Use VMWare Workstation. Why? You get much better interactive performance when developing.
Keep my personal and business stuff separate from my everchanging-upgrading-munging development work stuff	The host keeps all your basic apps - email, business, skype, fun, etc so you don't have to run vmware to access 'everything'. The host can also run the main dev db server and subversion (cause it's just faster I/O). But its in the background (right!).
Setup my VM for development	Use VMWare Workstation to run a development IDE in a Win2003/8 VM.
Test with my VMWare	Use VMWare Workstation to run as a test server in Win2003/8 VM. Real benefit is you can take a snapshot of your test vmachine and/or create a virtual test environment to handle an n-tier emulation, i.e web server+app server+db server. Just try to keep the test data (files+dlls + dbs) de-coupled from the Test VM so you can just roll back to the full Test VM for a new test run. If you have spare hardware use you can VMWare server 2.0 as it can run the stuff in the background and you can access it from your main terminal (laptop, etc). But then you need to consider setting up DNS/DHCP somewhere. Still prefer the VMware Workstation all-in-one setup.

Repair VS 2008 SP1 install

I got fuddled up with my Visual Studio 2008 SP1 update. It just did not happen correctlly. Some bits were missing, like the new Entity Data Model template. After waiting for soooo long, it arrives. Then it doesnt install. mmm. Pain.

I know people who just hate LINQ-to-SQL (as if it was my idea), but I do like it. It works. And it makes a well prepared way for a perhaps good successor, if it installs!!

So I found the fix. After you complete the install, run your VS Command prompt. and type

devenv /setup

then wait.

see http://msdn.microsoft.com/en-us/library/ex6a2fad(VS.80).aspx

The open VS, create a new class library, select add new item and there it is. New toy or your future bread n butter. Thats for you to find out. :)

Reporting Services Export formats - ASCII CSV and more

It seem Reporting Services is quite extensible. After much discussion around how we can provide a decent way to post-process a CSV file generated by an RS report, we found that we can add endless export formats (scary!) to a report.
Typically, out-of-the-box we have a few, namely CSV (unicode), PDF, etc. So we needed CSV in ASCII, with no headers. Umm! stumped for a bit, then the general problem-solver goes into motion and we come up with standard ideas of how and what more. But wait! There is simple answer there.

1. Open your C:\Program Files\Microsoft SQL Server\\Reporting Services\ReportServer\rsreportserver.config
   


2. Scroll down to <Render> section and you will see -
   

    <Render>
             <Extension Name="XML" Type="Microsoft.ReportingServices.Rendering.XmlDataRenderer.XmlDataReport,Microsoft.ReportingServices.XmlRendering"/>
             <Extension Name="NULL" Type="Microsoft.ReportingServices.Rendering.NullRenderer.NullReport,Microsoft.ReportingServices.NullRendering" Visible="false"/>
             <Extension Name="CSV" Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering"/>
             <Extension Name="IMAGE" Type="Microsoft.ReportingServices.Rendering.ImageRenderer.ImageReport,Microsoft.ReportingServices.ImageRendering"/>
             <Extension Name="PDF" Type="Microsoft.ReportingServices.Rendering.ImageRenderer.PdfReport,Microsoft.ReportingServices.ImageRendering"/>
             <Extension Name="RGDI" Type="Microsoft.ReportingServices.Rendering.ImageRenderer.RemoteGdiReport,Microsoft.ReportingServices.ImageRendering" Visible="false" LogAllExecutionRequests="false"/>
             <Extension Name="HTML4.0" Type="Microsoft.ReportingServices.Rendering.HtmlRenderer.Html40RenderingExtension,Microsoft.ReportingServices.HtmlRendering" Visible="false" LogAllExecutionRequests="false"/>
             <Extension Name="HTML3.2" Type="Microsoft.ReportingServices.Rendering.HtmlRenderer.Html32RenderingExtension,Microsoft.ReportingServices.HtmlRendering" Visible="false"/>
             <Extension Name="MHTML" Type="Microsoft.ReportingServices.Rendering.HtmlRenderer.MHtmlRenderingExtension,Microsoft.ReportingServices.HtmlRendering"/>
             <Extension Name="EXCEL" Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering"/>
         </Render> 

   
   
3. That's where the 'pluggability' is at. Each extension has a Renderer type. For simple stuff, like mine, just copy the CSV element and paste it back in. Rename the Name attribute to "CSV2".
   


4. Add overrides for the name that is displayed in the report dropdown menu - see CSV(ASCII)
   
5. And add DeviceInformationSettings in xml - the whole thing should look like..
   

   <Extension
     Name="CSV2"     Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering>
     <OverrideNames>
      <Name Language="en-UK">CSV(ASCII)</Name>
     </OverrideNames>
     <Configuration>
      <DeviceInfo>
       <Encoding>ASCII</Encoding>
      </DeviceInfo>
     </Configuration>
   </Extension>

6. Save it back (hope you got a backup copy of the config just in case)
7. Go to IIS (Control Panels/Admin..Tools/Internet Inf...), find ReportServer under Application Pools and recycle the pool ( so that the next report picks up the new changes
8. Done

If you need to write some funkier renderers, then consult MSDN. They have a standard api for it now.

Solve the problem don't create a solution

Problems are strange relatives. They turn up uninvited yet we know that some time or another they will turn up, invited or otherwise. No matter what we do, we can never truly prepare for their arrival, so it's best to deal with them when they turn up (with much courtesy if they are a difficult lot). Luckily for me, it's mostly good as we learn things when we get surprised.

But sometimes, they are a pain. Formalities, sensitivities and the bus load of other past life dramas. If you do decide to lend them a hand (thats more than a ear) you must be prepared to stand by that as you now become part of their system of problems. (see Systemantics)

Everyday or almost every day, we developers (designers, architects if so!), have problems to solve in our systems. We imagine how could we (or they) have designed it better. Often we build a new solution (see hand above) to replace the problem. That's good, but now we know we have promoted the problem (into a solution) so it will come back with more problems. Just be ready for them. Or if we could see a simpler way to solve the problem then do only that and let the problem remain a problem till reaches a point where a real solution is required to fix it and you know you are ready for the slew of new problems that will come with that system. No I am not lazy, I am just old enough to want to live the rest of my life. :)

Hopefully, our work problems vanish when they are solved. On the other hand, the problems or solutions of family and friends mostly only keep coming back.. with a hug ;)

Writing Use Cases

This is an article about writing use cases. Too many people have asked me for a set of rules to work with when dealing use cases. I am so tired of repeating myself that I decided this is the best way forward. For everyone, but mostly for me! As systems differ, so do the rules. As more BAs use them and provide me feedback, we can standardise what is in here.

>> link to document

Use Case Modelling Patterns

This is an attempt to capture commonly occurring patterns when modelling use cases and collaborations. The document covers

• Domain Entity Patterns

• General Use Case Patterns

• View Use Case Patterns

• Edit Use Case Patterns

• Search Use Case Patterns

• List Use Case Patterns

• Transactional (Web Service) Use Case Patterns

>> http://docs.google.com/Doc?docid=0AZ4gCMkMXW7bZGd6ODhjdjlfMTJjZzJzZzI&hl=en