June 2004 - Posts
I just installed the Service Pack 1 for .Net 1.1 (Beta). Great but does somebody know where I can find what have been done and improved on this upgrade.
Apparently the log I found in a temp folder seems to indicate that a lot of classes received a facelift.
Mark ask what do we think about the new MSDN Product Feedback Center.
Well this is just my opinion, but I quite like the idea. For me the think to vote for a suggestion is a great way to organise the priorities.
Maybe after few weeks, you should add more granularity in the products list. Now on a slightly negative note, I would say that this tool is quite dangerous for yourself.
It would be better that the growing bug and suggestions goes down rapidly before the final .Net 2.0 release. Otherwise you will see some complaints from the community to say that nothing has changed, you listen but you don't act.
Anyway I believe this is a really positive move, following the steps of the Microsoft blogging frenzyness, and the channel 9 adventure.
Ok now that the Microsoft .Net team got a short break after some good job in the past few months, can they answer this question.
When are we going to have a decent update for .Net 1.1, something like a .Net 1.2, including all the hotfixes, security patches, etc... ?
<rant>No I don't want to read 'wait the 2.0'</rant>
UPDATE: OK some good news a Service Pack 1 is on the way :-)
Check here the Technical preview (I think it's a Beta anyway)
UPDATE 2: And I can see there also a link for Service Pack 3 for .Net 1.0. It's about time !
In case you look for the docs, go here.
Well I don't want to be to tough there, but be careful with betas. History repeat itself, and I have this feeling that Beta 2 will add a lot of changes to Beta 1.
I read in different blogs some temptation to start real things with the Visual Express Beta 1.
Remember .Net Beta 1 in 2001 ? :-))
Long article but great one by Erland Sommarskog on searching data with many criterias.
I prefer myself stored procedure, but there you can find some good alternatives.
Well hopefully this will help somebody to avoid the same mistake.
Like many others I rushed on the new VS 2005 Express Beta 1. I installed on a machine with a previous version of .Net 1.1.
Thankfully this is not my main production PC. I run then in a series of small troubles, but like a coming storm, it gets to a point where I was unable to start any debugging session with a VS 2003 project.
I registered again the aspnet isapi dll under the .Net 1.1 folder but no hope, still an error (0x8013134b error code) when I was trying to debug the application.
The only cure I found was to remove completely .Net 2.0 from this machine. So obviously something goes wrong with different frameworks installed.
OK it's a Beta, but hey when you have a new toy, you want to play.
Thanks to Scott Guthrie to clarify this:
There will be a separate admin tool for SQL Express with the next beta. For Beta1 all admin can be done via VS 2005.
Hope this helps,
OK so SQL Express is on my machine, with already a SQL 2000 already installed. Now comes the surprise: no more snap-in to manage my databases ?!?
I tried to register SQL Express 2005 (which comes as an instance Yourmachine\SQLEXPRESS) using Enterprise manager. A message come to say that I need SQL workbench to manage my data.
So obviously I don't have any other tools except Visual Studio Express 2005.
My wish is for the Microsoft guys is that you make a separate manager for SQL Express 2005. IMO, it's much more productive and you can learn a lot by using different tools for a database or an application project.
I can't see the changes but anyway here we go with my favourite tool Reflector 220.127.116.11
More Posts Next page »