just needed to implement idisposable so i can use a class in a using clause and came upon this link
looks interesting and useful
Sunday, July 01, 2007
Saturday, June 30, 2007
Parser Error - Could not create type 'XXX'
i was creating a small test web service.
when i wanted to test it, but adding reference to another project, i got this error in the wizard 'Parser Error - Could not create type 'XXX''
and it suggested that i check the proxy settings blah-blah-blah
a quick search on google got me this, but i quickly found out the actual reason when i went to the iis settings - my test service was in .net 2.0, while the settings for the virtual directory were for .net 1.1
after i changed this all went smoothly....
just 2c...
when i wanted to test it, but adding reference to another project, i got this error in the wizard 'Parser Error - Could not create type 'XXX''
and it suggested that i check the proxy settings blah-blah-blah
a quick search on google got me this, but i quickly found out the actual reason when i went to the iis settings - my test service was in .net 2.0, while the settings for the virtual directory were for .net 1.1
after i changed this all went smoothly....
just 2c...
Thursday, March 09, 2006
mysql connector/net and cyrillics
im writing this application that stores client data in mysql 4.0.18 and i see that any data in cyrillics or unicode is stored as ??????.
wtf??
i search and search the web for solution and found .... nothing !?!?
i remembered i had a similar problem once with software for another client, and at that time a had given up and used MySQL ODBC instead.
this time i decided to continue the search and found this post (http://bugs.mysql.com/bug.php?id=10870) and a little bit somewhere here.
so the solution is to add charset=utf8 to your connection string.
why is it so hard to find the solution to a problem that should be common ? or, hmm, ok - maybe i really should've read the mysql manual properly...
wtf??
i search and search the web for solution and found .... nothing !?!?
i remembered i had a similar problem once with software for another client, and at that time a had given up and used MySQL ODBC instead.
this time i decided to continue the search and found this post (http://bugs.mysql.com/bug.php?id=10870) and a little bit somewhere here.
so the solution is to add charset=utf8 to your connection string.
why is it so hard to find the solution to a problem that should be common ? or, hmm, ok - maybe i really should've read the mysql manual properly...
Subscribe to:
Posts
(
Atom
)