32 bit IDE, 64 bit OS..,
-
String literals maybe, System.String certainly not. (I've had longer *nudge* *nudge*)
Agh! Reality! My Archnemesis![^]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server.I split a broadcast stream down into smaller chunks to speed up testing and 50K output was fine, tried a number of other and coincidentally larger streams which made things blow up and finally the original that I had split up and the same thing happened. Having found out about the 64K child limit on Treeview I am highly suspicous. :suss: This is .NET 2.0 BTW, I think a numbre of 16 bit length vlaues were changed to 32 bit in .NET 3.0
Join the cool kids - Come fold with us[^]
modified on Monday, July 19, 2010 4:23 AM
-
That's not an IDE limitation. A string is limited by a continguous chunk of available memory, not some arbitrary 16-bit number. I'd start looking to see if there is a big enough hole in the large object heap. The LOH doesn't get rearranged like the smaller heap does, so any holes created in memory will stay that way on the LOH.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008
But no longer in 2009... -
Tarkeesh Pradmanesh.
Agh! Reality! My Archnemesis![^]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server.Even Google doesn't help with that. Any clues?
-
Even Google doesn't help with that. Any clues?
-
.NET 2.0 has a number of components with 16 bit limitations, all I have to do is try and perusade work to support VS2008.
Join the cool kids - Come fold with us[^]
-
Don't even think of VS2010 - buggy as hell (never been there but have used an early version of Vista !) VS2008 is now mature enough for real use - never before Service pack 1!
-
Don't even think of VS2010 - buggy as hell (never been there but have used an early version of Vista !) VS2008 is now mature enough for real use - never before Service pack 1!
yeah, I think your problem may have been vista and not VS2010. VS2010 is fantastic on Windows 7 (64-bit). And you should be using the RTM version and not a Beta. Beta = buggy as hell + patience.
-
You having many issues with vs 2010? I migrated an asp.net project to vs2010 to test it out and quite happy with it actually, no bugs and the ui feels more responsive than 2008 but then again this is subjective.
Lots of problems with 2010, basically very unstable and can't be relied on. Using it mainly for native C++/MFC. When even their sample projects crash the IDE - you know testing is not high on the list! Some of our C# code has faired better. Its not just me , other engineers in company have similar if not more colorful descriptions of its reliability! No one wants to use it....... VS 2008 is fine - but had similar reliability problems before service pack 1.
-
yeah, I think your problem may have been vista and not VS2010. VS2010 is fantastic on Windows 7 (64-bit). And you should be using the RTM version and not a Beta. Beta = buggy as hell + patience.
-
I've been using it for C# and WPF development on 32-bit 7 since RTM and it's been reliable and stable. Must be a different animal for C++ then...
-
I've been using it for C# and WPF development on 32-bit 7 since RTM and it's been reliable and stable. Must be a different animal for C++ then...
-
Not one
constructor?Join the cool kids - Come fold with us[^]