none
what is unstructured project and how to structure it

    Question

  • i have the ame problem as mentioned

    http://social.msdn.microsoft.com/Forums/en-US/6c7a9c6c-d565-46ae-83ed-d39998c0fd41/eventtype-clr20r3-p1-devenvexe-p2-90307291-p3-488f2b50-p4-systemdrawing-p5-2000-p6

    the solution says that there was a unstructured project and structuring it in class libraries solved it...now how to confirm if my program is unstructured and how to structure it

    Monday, July 01, 2013 4:27 AM

Answers

  • i have disposed the create graphic() objects....i have a number of user controls and fonts  been used...but now disposing each  of them  is quite hard .........disposed the forms when the get closed ......i  I fill my dataset from the data adapter.....i have a records of about 12000

    You're having a CLR20r3 System.Drawing System.OutOfMemory issue. So I suppose you aren't disposing of something in a timely manner.

    Did you read up on detecting memory leaks and using a memory profiler (or whatever profiler it was) in one of your last posts that I responded to? It seems to me if you can't figure the problem out from looking at your code then you need to turn to an alternate, though maybe time consuming path, to resolve the issue. Which will also give you experience with new tools in case of future issues.

    Try downloading CLR profiler maybe if it still is used. The link is from 2004. Maybe there's a newer version or something.

    And 12000 records is what? Dust in the wind to a computer, that's what. Though why anyone would need 12000 records all at once is beyond me.

    http://msdn.microsoft.com/en-us/library/ff650691.aspx


    You've taught me everything I know but not everything you know. _________________________________________________________________________________________________________________ This search engine is for MSDN Library and has many features. http://social.msdn.microsoft.com/Search/en-US?query=search%20msdn%20library&beta=0&ac=8



    Monday, July 01, 2013 7:39 AM
  • Problem signature:
    Problem Event Name: CLR20r3

    Problem Signature 01:   call register.exe
    Problem Signature 02:   1.0.4744.35351
    Problem Signature 03:   50dc565c
    Problem Signature 04:   System.Drawing
    Problem Signature 05:   4.0.30319.17929
    Problem Signature 06:   4ffa5c71
    Problem Signature 07:   229
    Problem Signature 08:   18
    Problem Signature 09:   System.OutOfMemoryException

    An out-of-memory error in system.drawing usually means that you are trying to do something that GDI can't do.   It returns the out-of-memory error for almost any problem it runs into, regardless of whether or not there was sufficient memory. You need to find the exact piece of code that is triggering this error and rework it to avoid whatever the problem is.  Structuring your program inot class libraries isn't going to help unless your code is so complex that libraries are the only way to isolate the portion that is causing the problem.

    Monday, July 01, 2013 12:59 PM

All replies

  • So you're using the WPF designer and your Visual Studio crashes very often, without any apparent reason, and in various ways?

    I didn't see anything marked as the solution in the link you reference. Or even voted on.

    That's probably a question for one of the Forums for Visual Studio like maybe one of these two. Although I'm not sure the second one would be correct for you.

    http://social.msdn.microsoft.com/Forums/en-US/home?forum=visualstudiogeneral&filter=alltypes&sort=lastpostdesc

    http://social.msdn.microsoft.com/Forums/en-US/home?forum=vsx&filter=alltypes&sort=lastpostdesc


    You've taught me everything I know but not everything you know. _________________________________________________________________________________________________________________ This search engine is for MSDN Library and has many features. http://social.msdn.microsoft.com/Search/en-US?query=search%20msdn%20library&beta=0&ac=8


    Monday, July 01, 2013 5:11 AM
  • sorry for the trouble but i forgot to mention....we are not using WPF designer....and  we get the problem while running the exe of a vb.net application and the exact error is this way Description:
    Stopped working

    Problem signature:
    Problem Event Name: CLR20r3

    Problem Signature 01:   call register.exe
    Problem Signature 02:   1.0.4744.35351
    Problem Signature 03:   50dc565c
    Problem Signature 04:   System.Drawing
    Problem Signature 05:   4.0.30319.17929
    Problem Signature 06:   4ffa5c71
    Problem Signature 07:   229
    Problem Signature 08:   18
    Problem Signature 09:   System.OutOfMemoryException

    and in the post it is not marked as answered but Cristi Catalan(who initially posted) said (in post 13) that he solved his problem by structuring the project it in Class libraries

    Monday, July 01, 2013 6:18 AM
  • I suppose he or she means he or she made a bunch of the code in his or her project into separate classes which I suppose would result in having many class libraries. But who knows? He or she doesn't go on to explain. Perhaps when making he or shes classes he or she stumbled upon an issue an fixed it.

    Although your problem "System.OutOfMemoryException" isn't relevant to using classes as much as it is to disposing of something that is not being disposed of and is causing that problem most likely. I don't believe that using "class libraries" will resolve anything unless you find, while creating classes for your program, the problem in one of the classes. So I believe you will just be wasting your time creating classes.

    http://msdn.microsoft.com/en-us/library/ms973814.aspx


    You've taught me everything I know but not everything you know. _________________________________________________________________________________________________________________ This search engine is for MSDN Library and has many features. http://social.msdn.microsoft.com/Search/en-US?query=search%20msdn%20library&beta=0&ac=8




    Monday, July 01, 2013 7:10 AM
  • Also I would imagine that numerous of the errors listed at the following link, which resemble yours possibly, were corrected by various methods not requiring classes or class libraries or whatever.

    http://www.google.com/#sclient=psy-ab&q=CLR20r3+System.Drawing+System.OutOfMemoryException+vb.net&oq=CLR20r3+System.Drawing+System.OutOfMemoryException+vb.net&gs_l=hp.3...18057.27092.1.27344.24.18.0.6.6.0.231.2901.0j15j3.18.0...0.0...1c.1.18.psy-ab.FXbuoM3ggBk&pbx=1&bav=on.2,or.r_qf.&bvm=bv.48572450,d.cGE&fp=726653de331d681b&biw=1366&bih=622


    You've taught me everything I know but not everything you know. _________________________________________________________________________________________________________________ This search engine is for MSDN Library and has many features. http://social.msdn.microsoft.com/Search/en-US?query=search%20msdn%20library&beta=0&ac=8

    Monday, July 01, 2013 7:28 AM
  • i have disposed the create graphic() objects....i have a number of user controls and fonts  been used...but now disposing each  of them  is quite hard .........disposed the forms when the get closed ......i  I fill my dataset from the data adapter.....i have a records of about 12000
    Monday, July 01, 2013 7:29 AM
  • i have disposed the create graphic() objects....i have a number of user controls and fonts  been used...but now disposing each  of them  is quite hard .........disposed the forms when the get closed ......i  I fill my dataset from the data adapter.....i have a records of about 12000

    You're having a CLR20r3 System.Drawing System.OutOfMemory issue. So I suppose you aren't disposing of something in a timely manner.

    Did you read up on detecting memory leaks and using a memory profiler (or whatever profiler it was) in one of your last posts that I responded to? It seems to me if you can't figure the problem out from looking at your code then you need to turn to an alternate, though maybe time consuming path, to resolve the issue. Which will also give you experience with new tools in case of future issues.

    Try downloading CLR profiler maybe if it still is used. The link is from 2004. Maybe there's a newer version or something.

    And 12000 records is what? Dust in the wind to a computer, that's what. Though why anyone would need 12000 records all at once is beyond me.

    http://msdn.microsoft.com/en-us/library/ff650691.aspx


    You've taught me everything I know but not everything you know. _________________________________________________________________________________________________________________ This search engine is for MSDN Library and has many features. http://social.msdn.microsoft.com/Search/en-US?query=search%20msdn%20library&beta=0&ac=8



    Monday, July 01, 2013 7:39 AM
  • If you have a problem then better structure your project can help to find easier the problem.

    But it does not solve the problem.

    In an anology it is like telling that taking a betton road instead of the mud road if you have a flat tire.

    Like you see in these forums, the new CSS style sheet does not solve that I get small characters while typing in Chrome.


    Success
    Cor

    Monday, July 01, 2013 7:55 AM
  • Problem signature:
    Problem Event Name: CLR20r3

    Problem Signature 01:   call register.exe
    Problem Signature 02:   1.0.4744.35351
    Problem Signature 03:   50dc565c
    Problem Signature 04:   System.Drawing
    Problem Signature 05:   4.0.30319.17929
    Problem Signature 06:   4ffa5c71
    Problem Signature 07:   229
    Problem Signature 08:   18
    Problem Signature 09:   System.OutOfMemoryException

    An out-of-memory error in system.drawing usually means that you are trying to do something that GDI can't do.   It returns the out-of-memory error for almost any problem it runs into, regardless of whether or not there was sufficient memory. You need to find the exact piece of code that is triggering this error and rework it to avoid whatever the problem is.  Structuring your program inot class libraries isn't going to help unless your code is so complex that libraries are the only way to isolate the portion that is causing the problem.

    Monday, July 01, 2013 12:59 PM