Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Controls / July 2006

Tip: Looking for answers? Try searching our database.

Report Designer extremely slow

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Arturo Buonanni - 29 May 2006 16:11 GMT
Hello,

I've installed the Reporting Add-in for Visual Web Developer.
I had some initial trouble with the installation (the Reporting Add-in
package installs the report's dll in C:\Program Files\... with no
regard to where one really has installed the software that in my case
were D:\Program Files...) and now when I open an .rdlc file it takes 2
or 3 minutes to the VWD IDE to show it, even if it's just an empty
report.

Someone has an answer for this?

Thanks.
Arturo Buonanni - 01 Jun 2006 07:23 GMT
So none has ever had similar problem?

>Hello,
>
[quoted text clipped - 9 lines]
>
>Thanks.
Arturo Buonanni - 27 Jul 2006 17:01 GMT
It sound strange to reply to oneself questions but anyway, I've found
what cause Visual Web Developer to be so slow on loading .rdlc files.

The problem rise when the "Microsoft.ReportViewer.WebForms" namespace
is registered inside the application's web.config file. That happens
when you add a reference in the project to the
Microsoft.ReportViewer.WebForms.dll assembly.

I don't know why that (the slow-down) happens but if one get the
"Microsoft.ReportViewer.WebForms" namespace registration out of the
web.config file, rdlc files are opened in matter of second, if the
registration is present, it takes minutes to VWD to load up the rdlc.
And that doesn't happens just on my computer. I've tested two other
computers and the behaviour is the same on both.

I'm wondering wheter this is a known issue or not?

Now that I know that I'm facing another problem: I need that
registration somewhere because I've some utility code on a class that
works with objects from that namespace.
Where can I register the "Microsoft.ReportViewer.WebForms" namespace
other than the web.config file so that my classes can access it?

Thanks for the help.

>So none has ever had similar problem?
>
[quoted text clipped - 11 lines]
>>
>>Thanks.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.