.NET Wishlist (RSS)

.NET Wishlist

Windows .NET grid computing

Microsoft and grid computing

http://www.eweek.com/article2/0,1895,2009167,00.asp

and what if MS bought Digipede? I do hope they do!! I've used similar .NET grid computing software before in a financial services environment which could easily saturate 400-500 CPUs of parallel work on 4-5 different OSs and CPU types.

 

previous posts about Microsoft Windows Grid computing

http://weblogs.asp.net/ngur/archive/2004/09/14/229573.aspx
http://weblogs.asp.net/jan/archive/2004/12/29/343969.aspx
Free .NET Grid Computing software

What features does ASP.NET still need after Whidbey?

IMHO
workflow engine
web based job scheduler(DTS)
easier handling of stored procedures
better SQL injection/cross site scripting pretenction/prevention

Monad - petition

Can Monad be included in the Whidbey beta 2,
please please please.

 

Vote here on MSDN for Monad

.NET Collections - NEWS !!!

Brad Adams asks at http://blogs.msdn.com/brada/archive/2004/06/25/165992.aspx for help to expand the .NET Collections namespace.
This has been a sore point in .NET and am super happy that this is beeing addressed.

go to http://www.wintellect.com/powercollections/ and have a look

links
http://blogs.msdn.com/brada/archive/2003/11/18/50754.aspx

http://weblogs.asp.net/ericgu/archive/2004/06/29/169258.aspx

MSDN Product Feedback Center coming soon !!(Codename "Ladybug")

As noted at http://www.eweek.com/article2/0,1759,1617344,00.asp 
finally there will be a central place to submit bugs, feedback and feature requests.

Hardening ASP.NET - ASP.NET querystring parameter tampering - Part 3

Parameter tampering:

UPDATE!!! possible solution:

secure Querystring
http://www.dotnetjunkies.com/HowTo/99201486-ACFD-4607-A0CC-99E75836DC72.dcik
http://www.dotnetjunkies.com/Forums/ShowForum.aspx?forumid=4922

Vote here and here on MSDN  to have this functionality included in ASP.NET

From my quick and preliminary investigation of URLSCAN today I found out that the QueryString part of the url is not protected

To alleviate this issue of GET parameter tampering in ASP.NET I wrote up a little code with does the following:

- get the QueryString part of the URL
- decode it (HtmlDecode)
- parse out all the bad input
- limit the length of the queryString to minimum necessary

Since the HttpRequest class is sealed/not inheritable there are 3 ways to do it:

1) Write HttpHandler to deal with it
2) Extend Page class and set this functionality in prerender event
3) Write your own ISAPI handler in unmanaged code

I put one item on my personal .NET wishlist

 

.NET wishlist Issue 3

Please unseal HttpRequest class to allow integration of a HttpRequest validation engine

How about INETA to get an open source foundation???

First (Disclaimer):  I am not involved in INETA nor affiliated, but do follow its evolution

I'd like to ask if it would be a good for the .NET community, to pull together the best (20-30) .NET open source projects/free code bits in one place.

.NET wishlist Issue 2 (IPSEC and ADO.NET connections)

A connection to a DB from ADO.NET should be mandated with IPSEC, just as Forms Authentication requires SSL by default.

BTW, is there a way to detect if the connection goes over IPSEC.