I am trying to add a new report to a project in VS 2012. When I try to add a new report using the report wizard, I get a popup that says it could not load an assembly. The weird thing is that the assembly is not one that is referenced by the project.
Also, another developer opened the same project and was able to use the report wizard.
Does anyone know how the list of data sources in the wizard gets populated? It seems like it should be populated from the project, but I think there is something being populated in the data sources list that is referencing this assembly that does not exist.
Any ideas?
Related
I have installed Visual studio 2010 ultimate and when I try to open any window form from my existing window application project it gives me designer error as "The designer could not be shown for this file because none of the classes within it can be designed."
here is the image
Call Stack error message image
it works fine if I create new window application project, but giving problem for existing projects. Please help
Your question gives us very little to go on, considering you don't show us even a sample of the code that the designer is choking on.
My crystal ball tells me that you've created some custom control classes that inherit from other classes in your project. When the designer goes to load that custom control class, it tries to instantiate its base class, and so on up the inheritance hierarchy. If it doesn't find one of those base classes, it errors.
The solution is simple: make sure that you've built the application/library first, before trying to open any of its custom controls in the designer. That way, all of the dependencies exist and are available to the designer.
Another possible problem, along the same lines, is that your custom controls are using some functionality only available in the full version of the .NET Framework, but your project is set to target the Client Profile. To fix this, open your project's Properties window and change ".NET Framework 4.0 (Client Profile)" to ".NET Framework 4.0".
If none of that fixes the problem, the last glimmer I can see in my crystal ball is based off the name of the code file that you've shown us in the screenshot: ExtraServices.cs. That doesn't sound to me like the name of a control. It sounds like that's just a regular old class. If that's the case, you can't design it because there is nothing for the designer to display. The only code files that can be opened in the designer are those that inherit from System.Windows.Forms.Control or one of its derived classes (e.g. System.Windows.Forms.Form). Just right-click on it and open it as a regular code file.
I've created a DLL to a project in Visual Studio 2010.
I'm using this DLL in another project. Using the functions is completely possible - but I can't see any tooltip.
In addition - if I'm in the same project the tooltips can be seen.
I've read some issues about using the XML file with the name of the DLL in the 2nd project, but I'm afraid I don't have any XML file (as far as I see...).
I'll appreciate your help!
Lior
In the project settings of your DLL you can specify that a XML file will be created each time the assembly is build. Thi setting is located on the "Build" tab, region "Output" and is called "XML documentation file". Mark the checkbox in front and the xml file will be created.
When you use the dll in another project you have to copy the xml file along with the assembly file to have the IntelliSense information in place.
I have a winform project build on VS 2005 and framework 2. Recently, we moved to VS 2010, but keeping the framework v2 as target.
Everything runs fine except my web references.
When I update the web references, a new file "Reference1.cs" is created, under the reference.map file. This is causing troubles as original "Reference.cs" is still here and all classes are duplicated.
Here is the project structure :
My winform project
Web references
MyWebServiceReference
WebService.disco
webservice.wsdl
Reference.map
mycomplextype.datasource
Reference.cs
Reference1.cs
On the reference.map file, I have a custom tool defined : MSDiscoCodeGenerator. This custom tool seems to throw a warning :
Warning 1 A custom tool 'MSDiscoCodeGenerator' is associated with file 'Web References\MyWebService\Reference.map', but the output of the custom tool was not found in the project. You may try re-running the custom tool by right-clicking on the file in the Solution Explorer and choosing Run Custom Tool.
If I run the custom tool, the file reference1.cs is generated...
thanks in advance for the help.
I would try deleting the web reference and re-adding instead of updating.
I have a quick question....building a VS 2010 SharePoint project and I am referencing a custom assembly. I can reference this assembly in my code and it works fine to write code and all. When I deploy the project to SharePoint my Feature Activation code will not run because the custom assembly does not get deployed with the project.
I have set Copy Local to TRUE on the referenced assembly. Am I missing something?
Thanks
When you Create SharePoint Project in Visual Studio 2010, you will see a Item called Package in it.Click open it and bottom left corner click on Advanced, you will see an option to add additional assemblies , add as many you want > all assemblies you select here will get deployed as a Part of SHarePoint Package you create.
Not sure if this is what you're looking for, but you can use ilmerge.exe to bundle satellite managed assemblies into your executable, making it portable and more easily deployed. I use it all the time, it works great.
You can set up a build event in VS2010 to do this automatically whenever you build, too, though it can be a bit slow (I have it set as a Release-only build event for this reason).
I'm getting this error in visual studio 2008 in a Mobile Desktop application .NET 3.5.
Could not find type 'MyNamespace.MyType'. Please make sure that the assembly that contains this type is referenced. If this type is a part of your development project, make sure that the project has been successfully built.
This shows up when opening a form. The type that it can't reference is a user control that is part of the same project. Nothing is wrong with the namespaces. This is maddening -- the project builds just fine.
Also, the referenced control is not a generic class like in this article: "Could not find type" error loading a form in the Windows Forms Designer
UPDATE: well now later it seems to be working. This seems to be a sporadic problem...
Is the actual line that is causing a problem in the Form.designer.cs/vb file? Occasionally there are name qualification issues that result in the error you are seeing. Try opening up the designer file and changing the name as follows
C#
global::MyNamespace.MyType
VB.Net
Global.MyNamespace.MyType
After that, rebuild and reopen the designer