help.net
<font size="2"><br />Musing on .Net</font>
-
Martian Spirit :-)
-
Writing YABE (Yet Another Blog Engine) in ASP.NET 2.0
John Lam relate his experience on building a blog engine with ASP.Net 2.0. Brave man, because it's surely an adventure to play with alpha bits.
By the way John, do you have any place where we can see YABE ? -
A Journey of a Thousand Miles
Summary: Chris Sells begins his "Longhorn" Solitaire project at the ground floor, exploring the initial decisions developers will make when building new applications targeting Longhorn. (12 printed pages)
-
FreeTextbox 2 soon
It seems that some bloggers are aware about a soon to be release version 2 of the popular FreeTextBox.
The main changes seems to be the compatibility with different platforms and browsers( Mac, Windows, Linux, Mozilla, Opera, Netscape and of course Internet Explorer).
Revjon if you read this post, can you give us more details ?
By the way I just noticed that a version 1.6.5 is ready for download and it's dated 8th of February. -
TodoList 3.03
TodoList gets better and better. Check the last version. Cool !
-
Gush
Thanks to Stefano Demiliani for this link to Gush. Instant Messenger, aggregator, all in one, customizable and open source.
-
SMTP/POP3/Imap4/Webmail freeware
Lumisoft has developed a fully-featured Webmail C# app with sources and free.
Via Scott -
Error catch in Whidbey
I forgot yesterday t mention the cool way you can catch an error exception in Whidbey at debugging time.
You indicate which error you want to stop on, and when you debug, Whidbey stops and show you the line where you have the issue with a nice bubble and soem advices on how to fix the error.
Neat but one question. Does this system can apply to any errors ? I think about the type of errors like Internal Network Connection (mostly linked to SQL connections and the pool).
Can we will have a way to extend the list to some new errors ? -
Treemap demo
I just received this from Pat Piccolo:
-
Passing parameters to an ASP.NET page running in an IFRAME
I am building a content management intranet for my company. The website is based on DotNetNuke, and uses the excellent FreeTextBox control in order to enter HTML into the articles. One of the best features of FreeTextBox is that you can easily add your own buttons and functionality to the control. For instance, the built-in function for adding images didn't meet my needs. My images are stored in SQL server, and require a custom 'src' property in order to retrieve the image. No problem - I added a new button to the control, and built a small aspx page that opens in a modal (popup) window. The popup window allows the user to choose an image to insert, or upload a new image to be inserted. But that's where my problems began.
The Problem
If you've never tried to run an aspx page in a modal window before, then I've probably already lost your attention. But if you have, then you've most likely run into a rather odd problem. Just opening and running an aspx page in a modal window works fine, but if you need to do anything that causes a postback, a funny thing happens. The page opens up in a new window. Worse yet, the new window that opens doesn't have any of the data that you just submitted. The whole thing is a total wash. And javascript isn't terribly helpful. What to do?