I'm using Visual Studio 2010 Express for C# and am having trouble installing the code pack.
I downloaded the source from MSDN and don't know what to do with it?
I opened the WindowsAPICodePack.sln and attempted to build the project and got:
Error 16 The type or namespace name 'ContentPropertyAttribute' could not be found (are you missing a using directive or an assembly reference?) C:\Users\Joe\Downloads\WindowsAPICodePack\Shell\CommonFileDialogs\CommonFileDialogRadioButtonList.cs 13 6 Shell
and
Error 13 The type name 'IComponentConnector' could not be found in the namespace 'System.Windows.Markup'. This type has been forwarded to assembly 'System.Xaml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Consider adding a reference to that assembly. C:\Users\Joe\Downloads\WindowsAPICodePack\Shell\obj\Debug\Controls\CommandLinkWPF.g.cs 42 99 Shell
each about 5-6 times each.
I attempted to build the samples also but got similar errors.
How do I install the code into Visual Studio?
How do I fix the errors?
How do I include the code into my projects?
Can I make the Library usable in my projects with just a "using" command?
Add a reference to System.Xaml.dll to your project.
I've just downloaded version 1.0.1, opened it up in Visual Studio 2010 Professional and built it with no problems at all.
Check which version of .NET your projects are now targeting. It's possible that the Express edition automatically "upgrades" projects to target .NET 4, whereas mine have been left targeting .NET 3.5.
Another thing to check - do you have .NET 3.5 installed? I'd expect so, but it's worth checking.
When you've built the projects, you need to do two things to use them:
Add a reference to the built assembly (e.g. Microsoft.WindowsAPICodePack.dll)
Add a using directive to the appropriate namespace. (This is actually optional, but otherwise you'll have to use the fully-qualified name for any type in the library, which isn't generally what you want.)
Related
Everything is installed and everything is ready, but this problem occurs during compilation:
Error 296 The type or namespace name 'combit' could not be found. (Missing a using directive or assembly reference?)
Yes, we were able to solve it after a long time.
Our Project Version
Our project runs on .net 4.5.2.
Plugin Version
The latest version of Combit.Reporting is .net version 4.7.
In other words, it will not give any error, but it will prevent your project from compiling because the .net versions do not match.
Attention!
If you want to connect a project that needs a higher .net version to
your project, consider the above article.
A consultant modified our project (asp.net core C#), in VS15, to add a call to a SSIS package.
We are getting errors compiling this code in VS17.
using System.Data.Sql;
using Microsoft.SqlServer.Management.IntegrationServices;
using static Microsoft.SqlServer.Management.IntegrationServices.PackageInfo;
var intSvc = new IntegrationServices(new System.Data.SqlClient.SqlConnection(Database.GetDbConnection().ConnectionString));
....
....
Errors
Error CS0234 The type or namespace name 'Sql' does not exist in the namespace 'System.Data' (are you missing an assembly reference?)
Error CS0234 The type or namespace name 'Management' does not exist in the namespace 'Microsoft.SqlServer' (are you missing an assembly reference?)
Error CS0246 The type or namespace name 'IntegrationServices' could not be found (are you missing a using directive or an assembly reference?)
....
....
Is Visual Studio 2017 simply incapable of supporting SSIS calls? Or do I simply need to find these libraries and create explicit references to them?
Seems there is no support for SSIS in VS 2017 until VS 2017 update 3 (15.3) according to this link(June 2017).
Support for Integration Services for Visual Studio 2017 is in
progress, but is not yet available on launch day. For now we recommend
using SSDT for VS2015 if you need to use all of the BI project types
together in a solution, but stay tuned to this blog for updates
on this.
According to this discussion there will be SSIS support in VS 2017 update 3 (15.3), which was released yesterday (15.08.2017). It will be shipped like separate .exe installer. Here is quote from this discussion:
SSIS heavily rely on COM, and we have dependencies on VSTA, old SSIS runtime (to support multiple target server version), so we need an exe installer (like SSDT for VS2015 installer) to bundle everything. Our installer can be found in SSDT download page soon. I will let all of you know once it is released. Currently we are targeting this week or early next week, as long as everything goes well.
Have you tried to re-add references to those asemblies? Right-click on the Reference inside your project, click Add Reference and re-add all those assembies that are missing.
I have a vspackage that works fine in vs2012, but when I change the target to 4 or 3.5 to target older version, I get compile error :
Error 17 The type or namespace name 'PackageRegistrationAttribute' could not be found (are you missing a using directive or an assembly reference?)
and there is no reference to be added for microsoft.visualstudio.shell.10.0 and 9
Is it possible to create a vspackage in vs2012 for older versions ?
Thanks
Rather than add a reference to the Visual Studio SDK assemblies directly, you can add the appropriate VSSDK.* NuGet packages to your project. For example, the Shell assembly you are looking for to target .NET 3.5 (Visual Studio 2008) is VSSDK.Shell.9.
Note that Visual Studio 2010 includes .NET 4, so it is highly unlikely that you will need to build against .NET 3.5. Visual Studio 2008 and earlier did not support VSIX files to package extensions, so you're really going to have your work cut out if you want to develop an extension supporting those older environments.
I'm trying to experiment with Microsoft.Web.Administration on my Windows 7 x64 box, using Visual Studio 2010. When I add the DLL to references in my C# project, I can see its namespaces and classes pop up in Intellisense.
But as soon as I build, I get "The type or namespace name 'Web' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)", and I get build errors in the code I've written, as if the DLLs aren't even there.
There are two sets of IIS7 DLLs that I can see, in:
%windir%\system32\inetsrv
%windir%\syswow64\inetsrv
But both sets seem to do the same thing: Apparently initially work, then fail on build.
Does anyone know what I need to do to get this working?
If this is a .NET 3.5 or .NET 4.0 project, open the project properties. On the Application tab it will have probably defaulted to either of:
.NET Framework 3.5 Client Profile
.NET Framework 4 Client Profile
Change this to .NET Framework 3.5 or .NET Framework 4. Your project should then build just fine.
As the compiler error points out, Microsoft.Web.Administration has a dependency on System.Web which isn't referenced in the 3.5/4.0 client profiles.
EDIT: I modified the question title
after understanding the actual
problem.
I tried to run the sample RSS reader from Codeplex. I tried it on CTP version of the Windows Phone Developer Tools and it worked ok on that.
But now after trying it on beta version of the tools, it gave me following error.
The type or namespace name 'Phone' does not exist in the namespace 'Microsoft'
(are you missing an assembly reference?)
Its not able to locate the assembly Microsoft.Phone.Controls. Though I've installed beta tools successfully on my machine.
What could be the problem?
There are large changes in the namespaces and dlls between CTP and Beta. Most of the Microsoft.Phone namespaces have been merged into a single dll, when in the CTP they were in separate dlls.
You'll need to basically remove the invalid references you see in the project tree, and then resolve the missing references in each file.