Hi,

I?m using Visual Studio 2005 Pro to build an Asp.Net application.
This app has six step Wizard component, each one with a linked FormView.

When I choose an EditTemplate of the FormView that have a lot of components,
my Visual Studio goes crazy and allocates a huge quantity of memory.
He starts with 420MB and goes to 1.54GB.
In this case I need to use Visual Studio in source mode,
because in design mode it is impossible.

This EditTemplate have 25 fields that use TextBox components.

My PC is an Athlon XP 2.8 with 512MB RAM.

thanks.

Same problem , suddenly uses huge amount of memory, got an answer yet ?

I just saw this thread now and will forward it to someone to investigate.  I'm not sure what this is.

Thanks,

Scott

Hi!

I tried to repro this locally, and couldn't get VS to eat more than 210 meg of memory.  Can you send me a file that I can play with here and try to get it to repro here?

thanks,

PEte

---

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Pete,

How can I send my project to you?

Ricardo Barros

Hi Ricardo,

It is indeed a bug, thanks for letting us know.  I've filed a bug with our developers and we'll get it looked at as soon as possible, and hopefully get it fixed in the next SP, but no promises there.

You can check on the status of the bug by visiting http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackId=FDBK48006

Thanks!

PEte

---

This posting is provided "AS IS" with no warranties, and confers no rights.

I have the same problem without a wizard in my formview. I have a formview with a lot of controls in it. (50 textboxes and 20 dropdowns)

When will this problem be solved?? Is there a hotfix. Because of this problem i its hard to develop large forms.

 

 

Does anyone know if this has been solved?  I am having the same problem.  Running XP Pro, with 1gb memory.  If I have a formView template with 6+ labels, VS chews up 700mb of memory.  I have done a repair, the a complete uninstall/reinstall.  I've tried it on a different machine: same result.  This is making the FormView control basically unusable for me, and I *need* to have it available.  I followed the link posted by Patel - there doesn't seem to be any resolve from what I can see...hoping someone else knows a solution.

Thanks!

---

Scott L. Ellis

The reality is that the only fix that exists for vs 2005 crashes and other breaking problems is to use vs 2003.

Breaking problems simply dont get fixed with vs 2005 after all it is almost two yeasr since the release and all the breaking BUGS still exist today..

And there is NO light at the end of the tunnel with regards to SP1 which is like "everthing" from MS on the "never-never" path.

I see that after three years the SP1 for vs 2003 looks like actually making it, hence a quick assumption is that SP1 for vs 2005 could be about 2008...

Not sure any developrs can wait this ling to simple get vs 2005 to be usable..

 

Hence the ONLY solution is to stick with vs 2003..

 

 

 

 

 

 

I wanted to post to clarify Microsoft's commitment to servicing customers using Visual Studio 2003 and Visual Studio 2005.

As Pete mentioned in this thread, we've acknowledged this issue and are addressing it in the next available service pack for Visual Studio 2005.

Prior to that service pack being available, if this issue presents a significant impact to your business or usage of the product, then Microsoft will be happy to evaluate if it is possible to provide a hotfix directly to you.  To request a hotfix you should contact Microsoft Product Support Services - http://support.microsoft.com/.  The product team will then evaluate the hotfix request and if no reasonable workaround is available, and the impact to the customer is significant, the product team will make a hotfix available.

Please do not hesistate to contact PSS if you need a hotfix to a product bugs like this.  We'll definatley look into providing one if the issue warrants it.

Thanks,

---

Omar Khan
Visual Studio Web Tools

"I wanted to post to clarify Microsoft's commitment to servicing customers using Visual Studio 2003 and Visual Studio 2005."

The FACTs speak otherwise...

When MSoft knowingly relased a product with known braking bugs they said they would address these in SP1.. Now almost a year latter there is NO end in sight..

Conclusion based upon fact is MSoft is NOT committed to serviceing its customers...

Full stop..

"To request a hotfix you should contact Microsoft Product Support Services "

The same old rubbish...

See your onwn support site on why this apprach does NOT work,a nd why your custoemrs do NOT want this process.

MSoft reponse "MSoft policy is not going to change" so much for "commitment to servicing customers " what total rubbish..

Bottom line:

1. Stop the marketing rubbish, otherwise you start to belive it yourself..
2. Focus on getting at least one product right i.e fix 2005 before pending time on 2007 or any of the other rubbish..
3. get the basics right, i.e a compiler must be able to "compile" without crashing, locking up and must catch basic syntax errors at compile time, not runtime.
4. When you change something, ask yourself will this break existing code!!
If the anwer is yes, DONT DO IT..

How anyone could have made the changes to vs 2005 i.e before WAP is simply beyond belief!!

Lastely vs 2005 SP1 will contain what ( gee wiz no idea...) and will be relased when ( gosh also no idea)..

No-one belives anything MSoft say about anything these days, my experience is that Msoft can perhaps get somthing out that works about once in every five years..

Vs 2003 SP1 looks like it may make it before 2006, hence vs 2005 SP1 would be 2008!

Clearly there is NO ONE in MSoft who takes responsibility for anything...

 

 

 

 

I find it amazing that this is not an issue to more developers.  Maybe most developers don't use the FormView control, I don't know.  I have found that the limit for being able to use the designer to build the ItemTemplate, EditItemTemplate and InsertItemTemplate is about 12 controls per template.  Maybe 6 label/textbox pairs.  Beyond that, I get System.OutOfMemory errors and lose all the work that I have done on a template as VS2005 crashes.  So, if I'm making a FormView with small templates, I have to stop and build after inserting no more than two control pairs, just to keep from having to redo my work.  I am building a web application, not just a site, and I *NEED* the FormView control. (By the way, it's not just the formView control, but all data controls that exhibit this issue if template editing is involved).  I have a few FormViews and one DataView that have over 30 controls in each template.  Forget it...I have to all that programming declaratively.  And, no, it's not my machine.  I had 1GB memory, which I upgrades last week to 2GB.  That ought to be enough, don't you think?  I have no problems with other programs.  I can run Illustrator, Photoshop, Word, Outlook, Excel, SQL Server Dev Center, Explorer 7 with many tabs open - and I have no problem whatsoever.  As far as I'm concerned, with the work I do, this makes VS2005 unusable.  I'm too deep into this project to change now, but I'm certainly going to give FlexBuilder 2 a go for my next project.  No more more of this crap for me.

---

Scott L. Ellis

Based upon experience todate with yes, Apps not web sites, the problems are entirly due to vs 2005, vs 2003 works fine.. The same app side by side has no ( well none that matter) in vs 2003 and yes the crash and burn cycles in vs 2005..

Memory ( yes we have tried the 2 gig approach as well) makes no difference, the Hot fixes dont work either ( see the big project ones MSoft left out of vs 2005 when it was relased).

Yes it about time deevlopers stopped putting up with this Crap..

Anything less than a working product and updates delivered in the same way as Windoews and Office is simply not acceptable!

Perhaps we developers need to be more like general  business, and get together a class action to recoop our losses due to Msoft knowingly releasing vs 2005 with breaking bugs...

As MSoft simply does not care about developers, vs 2005 proves this...

 

 

 

Scott,

It would be really unfortunate if you stopped using Visual Studio based on being blocked by this bug.

If this is blocking your work and you want to make a hotfix request we can look at getting you a fix earlier than SP1 (probably within a couple of weeks).  If you would be interested in doing that please send me an email directly at omark-at-microsoft-dot-com and I'll get it started.

As I mentioned we are committed to fixing any blocking issues for customers so if this is truly blocking you I promise we'll get you a fix.

Omar Khan
Group Program Manager
Visual Studio Web Tools

---

Omar Khan
Visual Studio Web Tools

hi omar,

I would also like to register my interest in receiving the hotfix for this bug.  It?s pretty much a show stopper at my end for the project I?m working on. 

i'm sure you can appreciate the drudgery of doing everything manually, wiring up event handlers, etc

thanks
tim

Hi Tim,

I've asked our PSS person to reply on this post with information on how to request the hotfix.  If you don't see that in the next day or two, let me know (omark-at-microsoft-dot-com).

 

---

Omar Khan
Visual Studio Web Tools

thanks omar, appreciate the quick response.

tim

hi omar,

no response about the hotfix yet.  is there someone i can chase it up with?

thanks

tim

A fix is currently in the works.  However, the finished patch is not complete at this point.  Once we have an installable fix, I will post steps on how to get it.

Thanks!

Jerry Orman
ASP.NET Support

The fix for this issue in which you get high memory and high cpu while switching to design view when you have multiple controls in a formview/multiview control is complete.  Here is the process for obtaining the fix:

1. Contact Microsoft Support Services (info is at http://support.microsoft.com)
2. Ask for the hotfix from KB article 924331

The article is not public just yet as the patch was just completed, but you can get the hotfix now.

 Thanks!

 Jerry Orman
ASP.Net Support