VS2008 was written by incompetent fools
-
Seriously, today is the same thing. Change the XAML, the app either won't compile ( out of memory exception was thrown ), or once I restart the IDE and it compiles, it sometimes crashes, in the top InitializeComponent call, with an arithmetic overflow. Rebuilding the app without changing the code, runs just fine. All the people who think that is acceptable, raise your hands.
Christian Graus Driven to the arms of OSX by Vista.
They don't call it bleeding edge for nuttin :doh:
Todd Smith
-
Seriously, today is the same thing. Change the XAML, the app either won't compile ( out of memory exception was thrown ), or once I restart the IDE and it compiles, it sometimes crashes, in the top InitializeComponent call, with an arithmetic overflow. Rebuilding the app without changing the code, runs just fine. All the people who think that is acceptable, raise your hands.
Christian Graus Driven to the arms of OSX by Vista.
What made you think anything had changed from yesterday, or are you just getting rid of todays angst early. Surely you have something new to bitch about or are you spending so much time fighting VS that you have not had the opportunity to dip into something new? Is the memory issue only due to using a virtual environment maybe.
Never underestimate the power of human stupidity RAH
-
What made you think anything had changed from yesterday, or are you just getting rid of todays angst early. Surely you have something new to bitch about or are you spending so much time fighting VS that you have not had the opportunity to dip into something new? Is the memory issue only due to using a virtual environment maybe.
Never underestimate the power of human stupidity RAH
Mycroft Holmes wrote:
Is the memory issue only due to using a virtual environment maybe.
No, it happens when I run on a PC, also.
Christian Graus Driven to the arms of OSX by Vista.
-
Seriously, today is the same thing. Change the XAML, the app either won't compile ( out of memory exception was thrown ), or once I restart the IDE and it compiles, it sometimes crashes, in the top InitializeComponent call, with an arithmetic overflow. Rebuilding the app without changing the code, runs just fine. All the people who think that is acceptable, raise your hands.
Christian Graus Driven to the arms of OSX by Vista.
-
Seriously, today is the same thing. Change the XAML, the app either won't compile ( out of memory exception was thrown ), or once I restart the IDE and it compiles, it sometimes crashes, in the top InitializeComponent call, with an arithmetic overflow. Rebuilding the app without changing the code, runs just fine. All the people who think that is acceptable, raise your hands.
Christian Graus Driven to the arms of OSX by Vista.
Repost! :laugh:
Best wishes, Hans
[CodeProject Forum Guidelines] [How To Ask A Question] [My Articles]
-
Seriously, today is the same thing. Change the XAML, the app either won't compile ( out of memory exception was thrown ), or once I restart the IDE and it compiles, it sometimes crashes, in the top InitializeComponent call, with an arithmetic overflow. Rebuilding the app without changing the code, runs just fine. All the people who think that is acceptable, raise your hands.
Christian Graus Driven to the arms of OSX by Vista.
The definition of insanity is doing the same thing over and over again and expecting different results. If it failed yesterday and the day before, why are you so pissed off it doesn't work today? Did you expect the stars and planets to be more favourably aligned?
Cheers, Vıkram.
I've never ever worked anywhere where there has not been someone who given the choice I would not work with again. It's a job, you do your work, put up with the people you don't like, accept there are probably people there that don't like you a lot, and look forward to the weekends. - Josh Gray.
-
Seriously, today is the same thing. Change the XAML, the app either won't compile ( out of memory exception was thrown ), or once I restart the IDE and it compiles, it sometimes crashes, in the top InitializeComponent call, with an arithmetic overflow. Rebuilding the app without changing the code, runs just fine. All the people who think that is acceptable, raise your hands.
Christian Graus Driven to the arms of OSX by Vista.
You should have had a workaround by now. So move on!
You can't turn lead into gold, unless you've built yourself a nuclear plant.
-
Seriously, today is the same thing. Change the XAML, the app either won't compile ( out of memory exception was thrown ), or once I restart the IDE and it compiles, it sometimes crashes, in the top InitializeComponent call, with an arithmetic overflow. Rebuilding the app without changing the code, runs just fine. All the people who think that is acceptable, raise your hands.
Christian Graus Driven to the arms of OSX by Vista.
Perhaps a MFC rewrite?
"When you have made evil the means of survival, do not expect men to remain good. Do not expect them to stay moral and lose their lives for the purpose of becoming the fodder of the immoral. Do not expect them to produce, when production is punished and looting rewarded. Do not ask, `Who is destroying the world?' You are."
-Atlas Shrugged, Ayn Rand -
The definition of insanity is doing the same thing over and over again and expecting different results. If it failed yesterday and the day before, why are you so pissed off it doesn't work today? Did you expect the stars and planets to be more favourably aligned?
Cheers, Vıkram.
I've never ever worked anywhere where there has not been someone who given the choice I would not work with again. It's a job, you do your work, put up with the people you don't like, accept there are probably people there that don't like you a lot, and look forward to the weekends. - Josh Gray.
Ph'nglui mglw'nafh C'thulhu R'lyeh wgah'nagl fhtagn (been way too long since I had an excuse to post this; I had to google up the proper spelling :doh: )
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall
-
The definition of insanity is doing the same thing over and over again and expecting different results. If it failed yesterday and the day before, why are you so pissed off it doesn't work today? Did you expect the stars and planets to be more favourably aligned?
Cheers, Vıkram.
I've never ever worked anywhere where there has not been someone who given the choice I would not work with again. It's a job, you do your work, put up with the people you don't like, accept there are probably people there that don't like you a lot, and look forward to the weekends. - Josh Gray.
The real definition of insanity is doing the same thing over and over again and getting different results. ;P
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Seriously, today is the same thing. Change the XAML, the app either won't compile ( out of memory exception was thrown ), or once I restart the IDE and it compiles, it sometimes crashes, in the top InitializeComponent call, with an arithmetic overflow. Rebuilding the app without changing the code, runs just fine. All the people who think that is acceptable, raise your hands.
Christian Graus Driven to the arms of OSX by Vista.
Hi Christian, just encountered this[^] and this[^] which may or may not be relevant to your VS2008 problem. :)
Luc Pattyn [Forum Guidelines] [My Articles]
- before you ask a question here, search CodeProject, then Google - the quality and detail of your question reflects on the effectiveness of the help you are likely to get - use the code block button (PRE tags) to preserve formatting when showing multi-line code snippets
