im building an application i started it in VB 2008 and i upgraded to VB 2010
then i made some mods and tryed to run the application and then
i get this error
Error2Reference required to assembly 'System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' containing the type 'System.Windows.Forms.Form'. Add one to your project.C:UsersAdminDesktop
[Code].....
I have managed to get ASP.NET Membership mainly working with my SQL server.The problem i'm having is I get an error in VS2010 in my code behind file when attempting to create a user. I get a Red Exclamation mark appear on .CreateUser on the code below.
Error Message:Reference required to assembly 'System.Web.Security.ApplicationServices, Version=4.0.0.0, Culture=neutral,PublicKeyToken=31bf3856ad364e65' containing the type 'System.Web.Security.MembershipUser'. Add one to your project.
Code:
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click
Try
Membership.CreateUser(r_user_name.Text, r_password.Text)
Label1.Text = "User created"
[code]....
I've tried adding the following to the web.config:Not sure if thats correct!! but i get an error message when I open the page:Parser Error Message: Could not load file or assembly 'System.Web.Security.MembershipUser, System.Web.ApplicationServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e65' or one of its dependencies. The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047)
I have a Visual Studio 2008 solution with project A referencing project B as a project reference. Project B references System.Data.Linq, but project A does not. Everything compiles and runs fine. I like this arrangement because avoiding a reference to System.Data.Linq in project A ensures that it uses project B methods instead of directly accessign System.Data.Linq methods, which I want to avoid.
View 3 RepliesWe are trying to write an application that uses the NServiceBus library in a VB.NET environment. We've been stymied by errors similar to the following: Reference required to assembly 'NServiceBus,Version=2.0.0.1071, Culture=neutral, PublicKeyToken=9fc386479f8a226c' containing the implemented interface 'NServiceBus.IMessageHandler`1'. Add one to your project.Our project already includes references to NServiceBus.dll and NServiceBus.Core.dll from the same NServiceBus 2.0 RC2 distribution.
[Code]...
Any ideas about how to solve this problem? (And, yes, my preferred solution is switching to C#, but no, that's not an acceptable one at the moment.)
"Warning1Could not resolve this reference. Could not locate the assembly "Dotnetrix.TabControl". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors." and i have no idea how to fix it. i need to use the dotnetrix.tabcontrol.dll for what im trying to do, but i can't build the program. i can debug it though. haha i am a complete newbie to visual basic but this seems to be my only problem so far.
View 8 Repliescan i know what .net framework is required for my application that has been developed under Microsoft Visual Basic 2010 Express.
View 1 RepliesWe have upgraded our project from Visual Studio 2008 to Visual Studio 2010 without any issues until now. Our project contains a folder call Libraries which contains different versions of Oracle ODP.NET DLL's as well as different versions of Telerik DLL's. Our project contains references to one of the versions of each. The problem is once we remove the reference and re-add it by browsing to the new version, again inside the Libraries folder inside the project, it adds the reference, but to the same version we just removed. We can even copy the DLL to our desktop, remove the reference and add to the new one on our desktop and it still will point to the Libraries folder version???. The only we we can actual change the reference to the new DLL is by manually changing the path in the .vbproj file, which is obviously not going to work for us. The same behaviour worked perfectly in VS 2008. We switch our references quite often, when new versions come out, but also far more often to QA different versions of ODP.NET and Telerik Control DLL's, so manually editing the .vbproj file is becoming quickly cumbersome. If I browse to a specific version at a specific path, Visual Studio should ALWAYS do what I'm telling it to do..
I did some seaching and came across a few other people with the same issue. This better not be as designed and if it's a bug, which I believe it to be, when will it be fixed?[URL]..
I've got an exception when I deployed my application: "the located assembly's manifest does not match the assembly reference" What I remember is changing the project name from the previous source code, does it affect that much?
View 1 RepliesI am trying to code an Auto clicker in visual basic and i am having issues that i believe involve user32.dll..
View 9 RepliesI am working on an application which compiles fine on machine that is Win 7 and 64 bit CPU. But when copy and I run the exe file on similar machine (Win 7 64bit) I get error message: Error: Could not load file or assembly 'Interop.ActiveDs.Version=1.0.0.0,... I have added ActiveDS Type Library 1.0 C:WindowsSysWow64activedstlb as a reference in the project file.
[Code]...
I made my first WPF control:
[code]...
On the DataGrid control it says: "the type datagrid was not found, Verify that you are not missing an assembly refernece" I'm creating the control within a Win Forms app. What assembly to I need to include and how do I do that in XAML?
I have VS 2005. I am creating a VB .NET class that will interop with a COM app. I want to add a reference to a type lib file (.tlb). So I run the add reference command and use the browse button. I browse to the .tlb file I want and ok out. When I am done, the reference I have is to an assembly in the GAC. But I don't want that assembly as a reference. I want to have the IDE create a private interop assembly that I will deliver with my .NET object.
So how do I avoid hvaing VB .NET pull in an assembly from the GAC instead of creating an interop asm from the typelib I have browsed to?
I am using VB.NET 2002 and we have set up a test environment running SQL Server 2005. I am trying to add a reference to Microsoft.SQLServer.ManagedDTS.dll which is required to run a DTS/SSIS package from VB.NET. However the dll does not show in my add reference listing so when I select BROWSE and select the actual DLL I get a rather long error message telling me that only 'dll' and COM components can be referenced.
The exact message is: A reference to 'C:Programs FilesMicrosoft SQL Server90SDKAssembliesMicrosoft.SQLServer.ManagedDTS.dll' could not be added. This is not a valid assembly or COM component. Only assemblies with extension 'dll' and COM components can be referenced.make sure that the file is accessible, and that it is a valid assembly or COM component.
I've just started working on a new project and have encountered an error of which I cant seem to fix. I've tried a few things but still no luck.
the error im getting is: Object reference not set to an instance of an object
[Code]...
while adding dlls through addrefrence . its poping up an error " Arefrence to c:... est.dll could not be added make sure that the file is accesible and that it is a valid assembly or com component "
the dlls are old versioned created in vb6
I have a pretty complicated project with lots of class files, code modules, etc. There was a changed to one of my referenced DLLs that requires an isolated change in a single Sub within my solution. Unfortunately, this new Sub is not compatible with most of my clients' configuration but is required by some of my other clients. So now I must keep two versions in Source Safe of my solution - which I do not want to do. What I would like to do is to be able to determine which DLL is running and flip a switch to use the either the old Sub or the new Sub. Currently the sub is in a class, but I could break it out. Is it possible to determine which assembly version DLL is running? Also, if I reference the new DLL, the old Sub will not build. If I reference the old DLL, the new Sub will not build. So is there a way to keep both Subs in the same project?
Can I use reflection to know what is the assembly version of a loaded DLL?
I have created a shared assemby MyLibray version 1.0.0.1 and installed it in gac. Again I created MyLibrary version 1.0.0.2 and installed it in gac.
See the gac screen shot.
But in Add Reference dialog box only older version 1.0.0.1 is available.
See the screenshot.
Reference Assembly outside the AppBase-Directory
View 1 RepliesI have an industrial control program that we install on OEM equipment. This equipment falls into one of two categories; those WITH a special piece of IO hardware installed on the computer and those without.
This IO hardware has .NET 3.5 support assemblies, and is easy to program for. In my program, I reference the assemblies under the Project Properties and I'm good to go. Here's my problem... my program now seems to NEED this assembly to even start up, even if I'm not directly accessing anything in it until much later in the programming. When we ship any version of this equipment; I need to install the IO hardware assemblies whether the equipment needs it or not just for my program to run. The assemblies are bundled onto a hardware driver disk, and this sucker is 3gig.
What I would like to do is alter my program so that it runs no matter if it finds those assemblies or not. If not, then it will automatically close off certain functionallities (you can't use that because your computer don't have the hardware installed); and ideally, Visual Studio won't have 100 errors about a "missing reference". If found, then it will call them and use them normally as the program currently does.
I have my forum calling a sub from a .DLL/Class Library and I get the "Object reference not set to the instance of an object" but when I had the .DLL as its own form, I did not get this error.
Here is the related code on the Form that calls the DLL:
vb
Imports ExcelImport.ExcelImport
Public Class Form1
Dim accConn As New OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:UsersAjDesktopTaxCert_be.accdb")
[Code] .....
I've got an project that whenever an exception is throw will generate an error log. It was debugging fine so I decided to build a test version to let some co-workers try out. The build didn't work exactly right and I had to alter some reference properties to get it to build. Now I have the following error, "Reference to a non-shared member requires an object reference."The red highlighted text shows "reference to a non-shared member requires an object reference.
Imports System.Data.SqlClient
Imports System.Data.OleDb
Imports Microsoft.Office.Interop.Excel
[code]......
I have a pretty complicated project with lots of class files, code modules, etc. There was a changed to one of my referenced DLLs that requires an isolated change in a single Sub within my solution. Unfortunately, this new Sub is not compatible with most of my clients' configuration but is required by some of my other clients. So now I must keep two versions in Source Safe of my solution - which I do not want to do. What I would like to do is to be able to determine which DLL is running and flip a switch to use the either the old Sub or the new Sub. Currently the sub is in a class, but I could break it out. Is it possible to determine which assembly version DLL is running? Also, if I reference the new DLL, the old Sub will not build. If I reference the old DLL, the new Sub will not build. So is there a way to keep both Subs in the same project?
View 1 RepliesI have been using the VB IDE for many months on a VB6 translation to vb.net 2010. I have had no troubles building and running in debug,until the message below just appeared. This now prevents me from running in debug. I have not used Publish in the Build menu or used ClickOnce. The Project - application page has "enable XP visual styles" checked. I do not want this unchecked, which will remove the error message below.
The error message is:
Error 2 Could not find file 'Microsoft.Windows.Common-Controls, Version=6.0.0.0, Culture=*, PublicKeyToken=6595b
[code].....
How to I reference my own .dll after i add it to the GAC? I successfully added my .dll to the GAC, have seen it in the list. However, when i try to reference in Visual Studios..... i am lost.
View 2 RepliesI explain what I would do immediately:I have to extract data from a table using html htmlAgility Pack This 'my code that when executed gives me' a reference error.I can not figure out what is wrong, I am more 'I can not do this
a Private Sub Button5_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button5.Click
Dim web As New HtmlAgilityPack.HtmlWeb()
Dim doc As New HtmlAgilityPack.HtmlDocument()
doc = web.Load("http://www.mia_pagina")
[Code]...
Currently, when I want to use Microsoft Chart Controls on a website, I need to add the following onto every aspx page where I want to use it:
[Code]...
Is there any way to move this to the web.config file, so that I don't have to put it on every page ?
When I try to compile my VSTO Outlook addin, I get this error:
Reference to class 'RibbonBase' is not allowed when its assembly is linked using No-PIA mode
I have Visual Studio 2010 and a VB Project that had a reference to Microsoft.Interop.Excel 12.0. Well recently I changed the reference version to 14.0. That was actually a mistake and now I need to bump it back down to version 12.0. However I get this error in my project now...
Project 'MyProject' requires a reference to version '14.0.0.0' of assembly 'Microsoft.Office.Interop.Excel', but references version '12.0.0.0'
of assembly 'Microsoft.Office.Interop.Excel'.
I tried removing references and adding the com object to, but no avail.
I am receiving this error: Reference to a non-shared member requires an object reference on the code I've
bolded within the code body. Here is my code:
[Code]...
I get this error:Reference to a non-shared member requires an object reference.When i compile on the following code section:
Private Sub statusBarToolStripMenuItem_Click(ByVal sender As Object, ByVal e As EventArgs)
ToolStripMenuItem.Checked = Not ToolStripMenuItem.Checked
statusStrip1.Visible = ToolStripMenuItem.Checked