We're using Reportviewer and rdlc files in our application. I had drillthroughs working fine and we put the app on the backburner to work on other projects. Now that the Users wanted a new build I revisited the app and tested with a new password in the connection string. To my surprise the Drillthroughs no longer work. To my further surprise I can't even click on the textbox that fires the drillthrough. I checked TFS and there have been no changes to the Report definition or the ViewModel that handles the Drillthrough. All I changed were the connection strings.
If anyone can point me in the right direction on how to figure this one out I'll be very happy.
I figured this out if anyone else is interested. I installed Visual Studio SP1 which apparently causes a few issues with ReportViewer.
Hi we have had the same problem and finally found a hotfix which works. You only need to download the file VS10SP1-KB2549864-x86.exe . Install and try again. Should work.
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=37409
Related
When working w/ a WinForm project in VS.NET 2015, our team has noticed that the mere act of opening a .VB form in the designer view (default action when double-clicking the file in Solution Explorer) will cause VS to modify many object properties in the "Windows Form Designer generated code" section of the actual .VB code-behind. It seems to be limited to the .Size and .Location properties for sometimes dozens or more of UI objects, always changing their X,Y coords just slightly.
Mind you we don't perform any action to drive this -- simply open the file (obtained from source-control and residing in the local solution/project) in VS.NET's form designer by double-clicking the file in Solution Explorer, and bam -- it has the "unsaved" asterisk and if you save it and compare to source control version you can see the modifications already made.
I couldn't find much on this. Is this a known behavior? Any idea why it does this? Kind of reminds me of the old days w/ MS FrontPage's designer view, and even the early days of ASP.NET in VS which would apply some HTML changes if you opened a WebForm in designer view, until they gave the option to disable that on a later release.
thanks for any input.
UPDATE: this appears to be continuing even with myself as the only editor of the .VB form in designer. various form elements are shifting their position very slightly. Here's a diff screenshot between my last check in and today, and I know I'm the only one editing:
...there are many like that. Always these two properties, always just a few pixels difference.
I don't have an specific answer for this, but since this drove us crazy a bit a few months ago with my team, while working on a WinForms project, I am glad to share my experience!
Every time someone opened any form on VS2015, it would ask other people who has the same solution open at that time to reload the code. We first thought the third party controls (at that time it was both DevExpress and Infragistics) we are using were re-generated on designed initialization - because they tend to do that a lot but then we realised this kept happening on forms that only contains .NET controls.
Now the funny part. This only happened to us on VS2015. We were using VS2013 before, without this annoying problem.
Long story short, then we realized the screens we are using have different DPIs, just like Cody Gray said. I am not absolutely sure if this was the reason, but since we started using TFS, obviously we don't have the problem anymore... Hope this helps somehow lol.
I have an SSRS report which drills through to sub reports via actions. The report functions correctly in the VS environment, and correct once deployed to the server and viewed through a browser.
The report however is also viewed inside our in-house app via a Microsoft.Reporting.WinForms.ReportViewer - and while it renders on screen correctly, clicking the element that would normally take me to a sub-report no longer functions.
I have had a look around and there seemed to be an issue around VS2010 SP1 where this stopped working, however I'm currently stuck with VS2008. This seems to be the majority of results I'm getting.
Anyone have any ideas?
Many thanks.
OK have found issue.
The text box in question had three place holders. A reference No, A date and an age. I wanted to trigger the sub report if someone clicked on the reference no. While this worked fine in VS and IE, it failed to work in the Microsoft Report Viewer control.
I have now set the action against the containing text box, rather than against a single placeholder/expression within that box. While this has solved the immediate issue that I have, it would not work if you wanted multiple actions from different placeholders in a single text box.
But for now, I'm all good, and all solved.
I am having a weird issue with VS 2008 when I go to debug my program. When I click on the play button to run the program it flashes real quick and goes back to the VB IDE. No matter how many times I click on the play button it continually flashes and then goes back without displaying my form window or anything.
What type of setting would I need to change in order to correct this issue? I've been through most settings in the "my project" section and i do not see anything that could be causing it to do something like this.
My older vb apps I've made seem to work just fine when I click the play button on them. Only noticed this problem whenever I go and make a new vb app.
update video of what's going on
http://tinypic.com/r/2eycaas/7
Try this?
"
Did we install some third party Add-ins in your machine? If we disable Add-ins (“Tools” | “Add-in Manager”) and run “devenv.exe /safemode”, do we still have the problem? This can eliminate the possibility that third party Add-ins are causing problems.
We also can try to run devenv /resetsettings (Commonly, it makes sense than re-installation) or devenv /setup in Visual Studio Command Prompt.
"
--http://forums.asp.net/t/1324737.aspx/1
Just check your output window.
Accessible from Menu-> Debug-> Windows -> Output. (Check image:1)
In output window select Show output from: Build combobox. (Check image:2)
This will give you perfect idea what is happening.
Following are the guesses.
The VBC installer is not installed or corrupted.
Some addon is registered to run before compiling and is creating problem.
....Long list until you tell whats shown in output window.
Also check Show output from: Debug in output window and Final check would be Immediate window.
I feel this three would give you hint whats going wrong.
Fixed.
Changing it to x86 instead of Any CPU worked!!!! :) But question is, why me having an Core i7 Quad doesn't support the program when i choose x64.....
David
Is the startup form correct? You can see that in project properties.
I'm developing a website with ASP MVC 3 and Razor in VS2010 SP1.
When I'm running the site from VS, if the view was open in the IDE, I can edit a view in runtime, and press F5 to show the changes, but if I open the view after run the site, then the view is locked (no message, simply I can write in the VS Editor)
When I stop debuggin the solution, the views that are locked remains locked, and I have to close the file and open id again in order to modify the code.
This behaviour is uncomfortable. Can anyone tell me why sometimes I can write in the VS2010 editor and other times I can't?
Other Notes:
The TFS is not the problem.
It happens in all the VS 2012 SP1 of my office.
It only happens in vb.net projects, not in C# proyects.
It didn't happens in VS2012.
I've disabled all the extensions.
Thanks.
I have experienced this as well.
I've found that just reopening the file, while in debug, works most of the time. The nearest thing I can figure is that you're not actually editing the file but actually viewing a debug version of the file.
This normally happens, for instance, a javascript method causes an exception within the source of that page. It then loads the active version of that page instead of the one you're editing. Though I've had it happen without any errors generated so I'm fairly certain that's not the whole issue. It might be worth posting an issue on http://aspnet.codeplex.com/workitem/list/basic It hasn't happened often enough for me to narrow it down but it sounds like it happens for you more often.
After more than a year suffering this problem, a solution was found.
This MS HotFix for VS2010SP1 solved the issue.
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=40811
I have a very basic Visual Basic Program that I created in Visual Studio 2010. It's a form application where clicking a button runs a simple calculation and then outputs the answer with MsgBox. When, I debug it works properly, however when I successfully build and run the exe, nothing happens. What could be going on here?
Are you doing anything like this?
Debug.Print(MsgBox("Your answer is 7. Try again?", vbYesNo))
In other words, are you making use of a library that is only available to a debugging session (in this case, System.Diagnostics).