On Visual Studio 2022, Windows 11.
Linq to SQL tools is installed from installer (Individual Components).
When right clicking a dbml file and View Designer, it just sticks on this and eventually needs an end task:
Tried (to no avail):
Clearing all app.config connection strings in the same project (in case it was silently barfing on one of those)
Installing older .NET frameworks, ticking on Data Storage and Processing and Data sources and service references
Any ideas what might be causing this? (Ran OK under Win 10 / VS 2022).
Edit: I've had this after every new PC install with Win 11, VS 2022 (3 work PCs), but it seems to resolve itself after a few days. I now know why, see marked answer re toolbox.
I experienced the same problem on Win8 with VS 2015 and 2017 and 2019, Win10 with VS 2015 and 2017. I did not solve the problem. Do not know what causes this problem. But now on Win11 with 2022 I opened my problematic DBML file, it took really long time to open (during opening it showed Not responding etc.) but finally VS opened DBML file. Then I made a change in the designer (just moved class a little bit = change = auto-generated file will be re-generated after save) and saved. Now this particular DBML file is opened within a second. Try it.
Viewing the Toolbox and (optionally) resetting it (right click > Reset) seems to solve this. It seems the designer can't open when the toolbox is not initialised (or fails to initialise). It is often a while before I open the toolbox on a new install so I kept on encountering this problem.
Related
I get this error some 23 times when publishing the website. There are no issues with compilation and testing. I know someone is going to have the urge to say "remove the duplicate reference from the web.config" but that's not the problem here. This is a project started in 2008 and the use of ReportViewer predates the code being added to our git repository (which in turn predated me working on it) so I know that nothing is technically wrong with the code. In fact, until last week, it published just fine. What changed? I finally got a newer, faster computer. The client wanted one line removed. I put the code on the new computer, removed the offending line, built, tested. All is ok. Then I went to publish and got the ReportViewer error. I'm working with a byte-for-byte copy of the project on the old computer and the only thing that fails is the publish on the new computer.
Clearly something isn't installed on the new computer that's preventing publish, but I don't have a clue what it is. (Or possibly something installed that shouldn't be. The "new" computer was actually in-use by another developer.)
I was grasping at anything for this problem. I got the idea to remove all copies of the ReportViewer DLL from the Microsoft.ReportViewer.WebForms folder. There were 5 different versions. Windows itself balked when I tried to move version 10. That was my clue. It turns out that whoever switched from version 10 to version 12 missed a couple of source files. I updated the reference to version 12 and the problems cleared up.
Now the real mystery is: why did it ever work on the old computer?
I have a SSIS package with script task, and is created in VS 2015. I am able to edit script task and opens in VISTA (VstaProjects), set a break point and shows there. But when I close the VstaProjects solution, the breaskpoint disappears in Scripttask in dts package and if I run the task in debug never hits the break point. I am using,
SQL Server Data tool : 14.0.61712.050
SQL Server Integration servcie Designed 14.0.1000.169
Visual Studio Enterprise 2015 v 14.0.25431.01 Update 3
Specifically to the problem of breakpoints not saving in the project: ReSharper might be causing this issue if you have it installed.
For me, disabling "Debugger Integration" in ReSharper options fixed breakpoints not being saved when closing the VSTA project.
When you set the break-point, you must build the solution; save it; close VSTA; then click on OK. Failure to do any of these steps will wipe out the breakpoint.
See my answer here for more details. https://stackoverflow.com/a/49640300/4630376
I have a weird problem in an windows phone 8 project (Visual Studio Express for windows phone 8) that Changes to xaml( ex:change visibility of control) don't reflect on App until I rebuild the project and deploy it again to emulator or device.
The changes reflect normally in the design window of visual studio but didn't reflect on the running App.
I did many researches and they didn't help, like:
1- Change "Build and Run" to "always build" when projects are out of date.
2- I checked configuration manager as This post suggests but it was selected.
I have the exact same issue. I have a work around at the moment to save the hassle of rebuilding the solution because rebuilding deletes and re-installs the app and changes any saved settings you've made while debugging. The work around is to switch between configurations. So I'll execute the app in Debug, make some changes, then the next time I execute I change config to Release, and the changes are there.
The difference I can see is when it works I can see the Build Output line which says "Updating the application as the manifest file has changed..." take a few moments to complete. When this issue occurs the output line appears for a split second and so you can tell the incremental deployment hasn't actually been deployed to the device/emulator.
This is a little frustrating so hopefully someone has a real answer. I have other projects on the same machine and they don't have this issue. Just the one project so I don't think its a VS2012 problem.
I've also tried suggestions from other sites saying delete bin and obj folders but that didn't work.
I had the same issue for some of my WP8 Silverlight projects in VS 2013. I couldn't understand why it happened only for some projects but not all, but eventually I found this forum thread. The solution is the following: if the name of your app includes spaces, you definitely need to remove them or replace say with the underscore char. This recipe helped to recover my 'problem' projects.
I also noticed that numbers at the beginning of app name cause the same problem. I solved it by removing numbers from solution and app name.
I've tried this on two different machines now on Windows 7 and it appears that the Window > New Window menu command is not available in Visual Studio 2010. It doesn't work for HTML, .aspx, and .js files, but does work for .css, .cs, and .xaml files. Has anyone else noticed this or knows why this is?
(I have the productivity power tools extension installed)
I found a registry entry at
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\10.0\Languages\Language Services\HTML]
or
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\Languages\Language Services\HTML]
for 64 bit machines
called "Single Code Window Only"
I deleted it and the menu command showed up!
Then I made a new window, and it was completely blank.
I checked with Visual Studio 8 and found the same thing. Apparently they have not implemented "new window" for some file types.
Apparently they had started to implement it for Visual Basic Files, but had it disabled because it hadn't been thoroughly tested yet ( http://msmvps.com/blogs/deborahk/archive/2010/05/17/visual-studio-window-new-window.aspx ).
I'm using the Crystal Reports Viewer 11 ActiveX control in an Access form (version 2007, 2003 format). Everything works well on my development machine, where I have CRXI installed. I copied the referenced DLL to the client's machine, but when I try to register it, it says "Can't find module" (I double- and triple-checked my spelling) and when I try to open the form it tells me "ActiveX component can't create object" when the code tries to create a new instance of the report object. I suspect there are more dependency files required by the DLL, but I'm a little at a loss as to what ones and how I go about finding out. Although I'm using the CR control, I assume this would apply to any ActiveX control throwing this error. Thanks.
There should be a runtime distribution document in your Crystal Help files - from past experience (Crystal 8.5) there are multiple files that you have to distribute and register.
I'm answering my own question in case someone finds this via a search in the future. I don't have the Access Package & Deploy wizard David mentioned above (okay, I probably have it but couldn't find it readily) but I image it would probably do what I needed, so I recommend anyone try that first. Instead, I was able to create a setup to install tghe needed files using the Visual Studio Installer and the Crystal merge modules; note that while it wasn't difficult, nor was it pleasant.
I downloaded and installed Visual Studio Installer 1.1 from MSDN. This creates a new project type in Visual Studio 6.0 (in particular, I used InterDev 6.0) that creates a Windows Installer (*.msi) setup file. Because one of the Crystal merge modules requires the Crystal license key and VSI doesn't support merge module parameters, I also had to use Orca, a merge module editor, available from the Microsoft Windows SDK (also available on the Microsoft download site). I recommend reading through the SDK and Orca pages on MSDN for more info. Using Orca, I was able to put my key code and recompile the merge module, so I don't have to deploy my key to my users, and my users don't have to enter one.
Again, the Package & Deployment Wizard is probably a better option, but when faced with using merge modules, as with Crystal, this method will get the job done.