I installed Crystal Reports for VS 13.0.2000 to work with VS 2010. I will need to use CR in a WinForm app.
To my utter surprise, I have no CrystalReportViewer in my VS Toolbox pane for WinForms. The CrystalReportViewer does show up in Toolbox for web forms though.
I could obviously add the viewer to my winform without using the toolbox, but I can not seem to figure out what do I need to reference to get it. I am already referencing all the usual dll's like CrystalReports.Engine and CrystalDecisions.Shared but it does not help.
Does anybody have any idea what I am missing?
You need to ensure that you're targeting the full framework, and not any subsets, such as the client profile
Related
I'm starting to develop apps on Xamarin, with Visual Studio 2017. As on WPF, there is a 'designer' window for the axml, with the view of the app itself, and a 'source' window with the xml describing the view.
My question is - can I split the windows so one will be above the other, just like as in WPF? Right now I can either view the designer or the source window.
Below are the wanted situation, and the current one. Thanks!
As far as I know, there isn't support to achieve that in Xamarin.Android on Visual Studio 2017.
Event if you try to use the split view and place the design in your left side you can't put the source in your right.
I know it could be overkill but most of the times I use Android Studio to draw my layouts. Since it support viewing the source and designer.
The split view designer feature for Xamarin Android has finally been added in the VS 2017 version 15.8 update. Here is a link to the release notes.
https://learn.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes
Android Designer Split View
First of all, I am completely new to Visual Studio, so please don't be too judgmental. I have a project I need to do in C# for my studies and my team uses a GitHub repository. I am in charge of creating the GUI and I am stuck at the very beggining.
I want to create the main application window using WPF, but when I use toolbox > choose items, I can not see the WPF tab. Also, when I am trying to enable the designer view, nothing happens.
Is it perhaps the software version being Visual Studio Community 2013 causing the issue? Do I need to have the Visual Studio Professional version in order to use WPF toolbox?
I'm attaching a link to the screen of the situation below.
As I presumed, all I needed was the professional version of Visual Studio. After obtaining and installing it everything works fine.
Installing WPF Controls onto a machine is a messy task.
I tested installation in various systems including VMs. Following are the issues I have seen.
Controls not installed in the VS Toolbox.
Controls are isntalled but, cannot be dragged-n-dropped onto the WPF Window
Duplicate entries in the Toolbox sometimes!
I do not know what is wrong with the ToolboxControlsInstaller package. It messes up the Toolbox all the time, well most of the times.
Any guidelines what is the best practices to install WPF controls?
Our customers are very annoyed with these Toolbox behaviors.
Any help is welcome!
Regars,
-Datte
Our customers were annoyed too.
So I wrote this tutorial article covering toolbox installation once and for all:
Visual Studio Toolbox Control Integration
The most convenient approach seems to be using the Toolbox Controls Installer (TCI) package already pre-installed in VS2010 and newer. This includes just adding a key in registry, i.e.
HKLM\SOFTWARE\Microsoft\VisualStudio\10.0\ToolboxControlsInstaller\SampleControl, Version=3.7.0.0, Culture=neutral, PublicKeyToken=3cc4c7b61201d46c
You can also specify a custom tab name.
If you don't have a custom installer for your components, wrapping the DLLs in a VSI or VSIX package may be convenient. The VSIX is more powerful, support quiet install, custom tab name and uninstallation, but only VS2010 or newer.
Be careful with registry + VS2012. I discussed how the registry should be updated for VS2012, or simply call:
devenv.exe /ResetSkipPkgs
and then
devenv.exe /Setup
To clear things up.
Sometimes one also have to clear the Toolbox cache (TBD files), which seems to be a quite evil thing!
How do you install WPF controls into toolbox? However, these are all common issues with Visual Studio toolbox if you(or someone while installing other components) have done some mistakes in configuring. Refer the below links which has suggestions to avoid these issues.
Installing controls to VS 2010 procedure : How to add my custom WPF control to the ToolBox by using the WPF ToolBox Control template
Icons messed up issue : Visual studio 2005 toolbox icons messed up (though this is not reported with VS 2010, this solution would work for VS 2010 also).
I am trying to use Crystal Reports ActiveX Viewer 13 from within Winforms. While SAP/BO has said they are not going to support this but I see the ActiveX control available on the machine. Any idea on how to use this control?
The Problem i'm facing with the the .Net Viewer is that it crashes on Windows7 if the OLEDB provider has any UI like parameters dialog. I posted the issue separately. One of the friend solved this issue by using Cr11R2 ActiveX Viewer. I am trying to find if it is possible to solve the issue by using the ActiveX Viewer that Comes wit CR for VS2010.
Any pointers in this direction is appreciated.
Found the Answer - The ActiveX control is still available for use with Webprojects. None of the supporting files to run on a Winforms application are avaialble so .. I guess one cannot use this option anymore
The ActiveX control is still available for use with Webprojects. None of the supporting files to run on a Winforms application are avaialble so .. I guess one cannot use this option anymore
I am using:
Visual Studio 2010 Professional,
Silverlight 4 Toolkit
The WPF Designer don't show (invisible) - while the Component Toolbox is showing the relevant controls, and the Windows->Windows option shows the designer to be active. It does this with ALL XAML for me, regardless of its complexity. I have already tried the /ResetSkipPkgs to no avail. I had CodeRush and DevExpress installed (demo) version but removed both since. I can get along with XAML by switching to Source Code /Text Editor, but this really boils my chops to run the app to find out that I have made a silly mistake in my XAML (while a preview would sort it out quicker, and no, please don't suggest Expression Blend for it is non-nonsensical for me to switch continuously between these applications).
When I however switch the WPF Designer to open with Encoding I get the following error - which I assume is related to the issue for not showing the XAML Editor/Designer in non-encoding:
An Unhandled Exception has occurred
Click to reload the designer
System.NullReferenceException
Object Reference not set to an instance of an object.
at MS.Internal.Providers.VSDesignerContext.VSDesignerContextHolder..ctor(IServiceProvider services, VSDesignerContext context, Object docData)
at MS.Internal.Providers.VSDesignerContext.GetContext(IServiceProvider services, IVsWindowFrame frame, Boolean createIfNotExist)
at MS.Internal.Designer.TabbedEditorPane.MS.Internal.Designer.ITabbedEditorService.get_DesignerContext()
at MS.Internal.Designer.DesignerPane.InitializeDesigner()
I have googled it silly, to no avail. I am thinking about reinstalling Visual Studio - but this REALLY is a last resort. I hate fixing things by reinstalling, rebooting etc.
Any guru with the magical answer?
I got the exact same exception today and solved it by killing a few GDI hungry apps. You can see the number of GDI objects a process is using in the Processes tab of Task manager (you will probably need to add the column using View -> Select Columns).
Hmm, I know this is old, but you should try installing SP1 for your Visual Studio if you haven't yet.