|
From: rowe_newsgroups on 1 Jul 2008 06:57 > Sure sorry your having so much trouble... But, I have had zero problems with > VS2008. Maybe it's VB thing though, because I mostly work in C#. Doesn't seem to be a VB thing, I work almost exclusively in VB now, and most of the developers I work with are doing 95% VB. I don't know of any problems from the other guys and I haven't had a single problem since 2008 was released. I am however running Team Suite so perhaps a version difference is to blame? Thanks, Seth Rowe [MVP] http://sethrowe.blogspot.com/
From: rowe_newsgroups on 1 Jul 2008 08:02 On Jul 1, 6:57 am, rowe_newsgroups <rowe_em...(a)yahoo.com> wrote: > > Sure sorry your having so much trouble... But, I have had zero problems with > > VS2008. Maybe it's VB thing though, because I mostly work in C#. > > Doesn't seem to be a VB thing, I work almost exclusively in VB now, > and most of the developers I work with are doing 95% VB. I don't know > of any problems from the other guys and I haven't had a single problem > since 2008 was released. I am however running Team Suite so perhaps a > version difference is to blame? > > Thanks, > > Seth Rowe [MVP]http://sethrowe.blogspot.com/ LOL Apparently I just jinxed myself. I just received my first crash in Visual Studio 2008. When using Ctrl+M+L to expand my code file the Visual Basic Compiler went kaboom. That'll teach me to say I haven't had any problems! :-) Thanks, Seth Rowe [MVP] http://sethrowe.blogspot.com/
|
Pages: 1 Prev: UpdateCommand problem Next: Enumerate and modify a dictionary |