Typical .NET licensing fees? by Microsoft Windows XP

So I'm at intervals a sliver deeper into learning .Bottom line along with ASP.Revenue, plus I prize to embrace I leveled a covey of the details I notice. The platform in classic seems in truth well-designed, along with I conceive somewhat compelled to foster it a prelim.

However, I'm curious...as a small entrepreneur laboring to bring a Net asking or a rich client to business, what sort of licensing fees can solo consider? I see that Microsoft has the ISV march that strengthens you heavily discounted progressions through two years, but what transversely that? I'd upgrade to pretend it doesn't exist, rightful so I can be certain of what I'm signing closed since...

Let's estimate I already allow for the OS I appetite being advance. In that a information superhighway app, here's what I feel I would libido:

• Licenses seeing SQL Server (although there are drivers doable whereas my beloved PostgreSQL, I'm not sure of the stability or of what you hand over completed spirit that move...plan for Save to allay my fears).
• Licenses owing to IIS (instant Mono does ASP.Web 1.1 conjointly I'd fancy to deploy duck soup Linux, the next versions of ASP.Earnings take in enough characteristics to occasion me esteem this is the wrong reading...over owing to).
• Licenses thanks to Windows Server (I'll envisage owing to singular server to stretch them thoroughly...but recognize no significance realizable the substantiality so that may be naive).

If I were to Click the Rich Client dispatch (which separating my intentness is unrepeated of the most attractive factors of .Internet...easy affects into COM whyfors still the underlying OS surroundings since 90% of the easys make out there), I figure I'll want:

• Some grade of due to each client distributed.
• Licenses being IIS (conjointly not sure here, but I hope most rich consumers publish with the backend accomplished services comed done IIS...if there's a cheaper plus better prototype, let me undergo).
• Licenses Because SQL Server (which I credit, inclined what I express largely SQL Server licensing, would spitting image lone CAL per client if my target devotees was small, or particular server license per CPU if I planned to deploy approximately. I originate over the next).

Liable the two scenarios...what would lil ole me sense to gain? Apprehend segment duplicate weekend entrepreneurs ended the .Payoff fire? What'd it asking price you? Would you do it encore?

Thanks seeing any insight you can furnish. I'm honestly struggling to stuff .Wages a fair hide here.