I don't blog much, but maybe now that i have installed BlogPress this will change?
Only time will tell...
Tuesday, November 23, 2010
Tuesday, September 14, 2010
After 3 years running with the same system (XP 64 bit), I finally decided to move on - and install Windows 7 Pro 64bit. I had been waiting for this step in order to also move to VS2010.
Monday, May 10, 2010
How good is your watermelon? See: http://delafranco.com/iwatermelon/
Do you want a hot iPhone girlfriend? See: http://www.mygirlapp.com/
Disclaimer – I don't know these guys, and never actually used these apps (I don't even have an iPhone), but I found the ideas cool (even if a little .. freaky).
Posted by Ilan Assayag at 10:53 AM
Wednesday, April 28, 2010
Wednesday, March 31, 2010
Directly from Mark Russinovich's blog: http://blogs.technet.com/markrussinovich/archive/2009/11/03/3291024.aspx
Amazing, insn't it?
Posted by Ilan Assayag at 1:44 PM
Wednesday, October 22, 2008
When using Linq-to-SQL with the dbml designer, by default it generates an App.config file and puts the connection string to use in it. This is fine (well, not really, but at least it works) for applications, but when working with class libraries it's a problem – DLL's don't load the app.config, so changing the connection string in the app.config won't produce any change (the application will still try to use the connection string that was used at design time).
I found a pretty neat solution here by David Klein ( http://ddkonline.blogspot.com/2008/02/set-connection-string-in-linq-dbml-file.html ), which is based on Jon Gallant's solution ( http://blogs.msdn.com/jongallant/archive/2007/11/25/linq-and-web-application-connection-strings.aspx )
P.S: The problem is known by MSFT: http://msdn.microsoft.com/en-us/library/bb386996.aspx . It doesn't seems to bother them though…