.net - Reference 2 Dlls Using The Same Namespace In 3.5 Project?
Jun 29, 2011
I have a vb.net 3.5 class library project that needs to reference two assemblies that have the same namespace. We have two third party dll's in which one is version 5.1 and the other is version 6.1. They have the same dll filename and they utilize the same namespace and functions/class names. The project needs to use one or the other depending on a specific situation. I've investigated up on a c# process that uses the "extern alias" feature to pull in the different assemblies.
[URL]
What use is the Aliases property of assembly references in Visual Studio 8.It seems that this feature isn't fully available for vb.net. Things I've Tried I've renamed the 2nd dll and added both references to my project. At this point I get tons of: 'blah' is ambiguous in the namespace. So I need to alias the different versions. In vb.net you can do aliases on an imports statement like:
Imports version5 = Somedll.Something
The problem is I can't setup an assembly reference alias for the different versions of the dll. Apparently in vb.net you can't set these up in the reference properties window. So I tried setting them in in my project file like this:
I have a simple vb.net project that outputs a dll. In order to build this project, I have to reference some 3 3rd party dlls by manually adding them to the project and then building.
What I want to do now is auto build this using a app called CruiseControl. . . I have been told that in order to use the 3 3rd party dlls, I have to modify the .proj file to include the .dlls. The thing is, where in the proj file do I include this and how do I do this? I think I may know where the section is and I have included it here:
[code...]
When I run the auto build program it fails (it runs through but fails at compile time); when I build this manually it works when i refer the dlls. What am I missing to make this work?
I have 2 projects, one built in VB.NET and another in C#.NET. I want to use certain functionality of VB.NET into C#.NET and hence I have added the dll file of VB.NET solution into C#.NET as a reference by browsing the dll from my system. Say dll name for VB.NET is myData.dll. In my C#.NET project I am trying to declare it as a namespace i.e. "using myData;" and its giving me an error of "Type or namespace name could not be found"
good way to run windows script host code from vb.net? Im trying to run some dsf com components but they are only for the 64-bit version of scripting engine installed. I wish i could execute my code from vb.net but sometimes it doesnt want to work because im referencing the 32-bit version script control and not the 64-bit scripting environment.
So my goal out of this is to find a 64-bit scripting component dll or library that i can use for executing a wsf file thats mostly written in vbscript but has some xml from the windows script host.Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda
I have a project that references two DLL files in the system 32 directory as COM references. The files are certenroll.dll and certcli.dll which are included in the system32 directory as part of the OS. My app is a console application that I'd like to have as a standalone exe. It seems that the these files are converted to something like Interop.CERTENROLLLib.dll and Interop.CERTCLIENTLib.dll and dropped in the bin directory for my project. Since I want the app to be a standalone exe able to run on other PC's I'd rather see the app reference the original DLL files in the system32 directory and not have to carry these dependency files around with it.
I have created an application and a setup application for it.The application references Microsoft.mshtml.dll and another custom dll.The problem is that despite the fact that i added to the setup project the output of the application, these two dlls were not added in the setup project's "detected dependencies". Do i have to add them manually ? Do you know if Microsoft.mshtml.dll (C:Program FilesMicrosoft.NETPrimary Interop AssembliesMicrosoft.mshtml.dll)will work both on Windows XP and Windows Vista no matter what version of Internet Explorer is installed ?
Years back I inherited a project that is written in VB.net - the problem with this site (it's a website in Visual Studio, not a web application) is that if you change any code you have to compile and upload the entire site each time.
Why? Because it seems to generate a bunch (maybe 10-15) of randomly named DLLs in the BIN directory on every compilation. Each page in the site then references these randomly named DLLs so I have to upload them all and the new DLLs if the site is to continue working.
What 'setting' is this site built using, or more importantly how can I change it to a more convenient system of generating one or two consistently named DLLs?
Let say I had a project contains 10 forms and 10 reports and typed dataset (xsd)I am trying to divide my project forms into dlls, so when the client had a problem or asks for modification in single forms, I had to build the project all over again and the exe size will be large.
in my current project, the exe size is 4.8 MB, and I am working with customers by internet and remoting, so every time I make small changes (change the back color of textbox in one form) I had to rebuild and send the whole 4.8 MB to the customer. And not forgetting the increasing size of the exe with time.I know that converting my project to class library and built it will convert it to dll, so I had to create a second project to manage it.
1 - Can I convert 3 or 4 forms / 10 forms total in my current windows application project to dll?
2- What is the best recommended method to divide the project into smaller entity.
I'm writing a piece of software that accepts XML from our clients. The xml has2 parts, a standard part that contains set fields, and a freeform part that allows our clients to add own their own xml
When I'm coding in Visual Studio 2010, say that I have some interface: Namespace Some.Huge.Terrible.Namespace.Adhering.To.Company.Standards Public Interface MyInterface ... Property SomeThing as String ... End Interface End Namespace
And a class: Public Class CoolThings Implements MyInterface
When I hit Enter after MyInterface, Visual Studio will put Property SomeThing as String Implements Some.Huge.Terrible.Namespace.Adhering.To.Company.Standards.MyInterface.SomeThing
I would like it to, instead, simply put: Property SomeThing as String Implements MyInterface.SomeThing
It does the same thing for all methods, etc. that I have to implement and it's mildly annoying to either have to look at a stupidly long reference, or clean it all up since I'm importing the namespace at the top of my class anyway. Is there a setting in Visual Studio that I can use to switch that?
I am trying to understand how to interact with external DLLs written in C++ for use in my VB.NET application. I have some DLLs that a client wrote that do some math functions. Everything was working on a 32-bit machine. Because we were taxing the 32-bit machine we moved to 64-bit. Now we can't get the same functions to work. The DLLs were re-compiled as 64-bit DLLs and they still don't work. So my client wrote some dummy DLLs to see if we could figure out the problem. Here are the "signatures" of the DLL calls that I am making:[code]....Ultimately I would like to get to calling initialize_quiet and I am guessing at the format of the marshalling, const size etc.
I'm developing application that is plugable. The plugins are loaded via Assembly.LoadFrom(). In my solution I have 4 projects. A WPF, 2 DLL and another DLL that is a plugin for the app. The plugin project references one of the other DLLs. When I build the Solution and run I was getting an error trying to use the plugin dll because it was expecting an older version of the referenced project. I had to clean and rebuild the plugin project to get it to run correctly.
I'm trying to make more use of namespaces and giving my project a more rigorous design, as it has been getting pretty messy.I was wondering,before I get started, is there a standard convention for the names and organization of namespaces?For instance,for a 3-tier program, should there always be a "UI", "Business",and "DataAccess" namespace (and is this what they're typically called)?Or should I just organize the project as I see fit?
I want to use project B property in project A. Hence, I added project B to my solution. How can i use the property of B? Can someone guide me? i'm new to vb.net..To my knowledge, we need to use namespace and create a new instance. Could someone guide me on how to use namespace for this purpose?
I'm developing an web application using VB.Net, and I would like to know, if is there any way to make a namespace to be viewed by all project without necessary Imports?
I have an VS2008 solution with 2 projects, WebUI and Domain; WebUI references domain. The Root Namespace in the WebUI project is:MyCompany. MyProjectName.WebUI. The Root Namespace in the Domain project is blank. (Namespaces are manually declared for all classes). So everything has been working fine, until I tried to reference a class in Domain via a fully qualified path: [Code]
Does this make any sense? So, then I cleared my WebUI Root Namespace, and voila, the fully qualified declaration then does work. However, doing this then seemed to invalidate the registration of all my user controls on my pages. The only thing that seemed to solve this was in the codebehind of each user control, manually add a namespace of MyCompany.MyProjectName.WebUI. which might make sense as perhaps the namespaces of the pages somehow had still retained the root namespace value. But, if I was to create a brand new aspx page and drop a user control on (this is before manually adding the namespace), even that page couldn't properly register it. Yet, the user control properly rendered in design view. so the VS UI seemed to be able to properly resolve it, but the compiler seemingly can't.
So from what I can tell, I can at least get things to work by manually wrapping user controls in the proper namespace. Why this is necessary for aspx pages, that have no namespace specified, to see the user controls, seems to make no sense. Is there some fundamental principle I am misunderstanding??
For a test scenario I have a dll project. In the project I have 1 generic class 'GlobalData' and 1 form 'form1' in the generic class I would like to make a public shared newForm1 as new form1 the line of code I'm trying is: Public shared newForm1 as new form1 I get the error newForm1 cannot expose type 'form1' outside the project through class 'GlobalData'. I really need to be able to make a public shared reference to form1. Any way to get around this? Background as to why I need to do this: I have several projects that need to use Form1 as a mdi child. I would like to just update the dll and not have to go back and update the same form in 50 projects.
I am trying to create a custom LabelFor helper to apply by default instead of the standard LabelFor helper include in System.Web.Mvc.Html. I want my LabelFor to take model properties that are PascalCase and make a label that appears as multiple words. For example the property FirstName would appear as "First Name".
I found this post that shows how to make a custom LabelFor helper that allows the addition of html attributes. I recreated this helper in VB.Net and modified it to do what I want, but I am not able to get it to work.
[Code]...
The sample includes this Module in Namespace System.Web.Mvc.Html but when I add the namespace declaration to this module everything in the rest of the project goes haywire. For example, each of my models has a Primary Key property that is a Guid datatype and as soon as I add the namespace above to the module, I get several errors stating that System.Guid is not defined among other similar errors.
I've tried to import my project namespace into a view in order to use the custom helper, but then I get an error that says Overload resolution failed because no 'LabelFor' is most specific for these arguments.I am trying to avoid having to specify a DisplayName for every PascalCase property I have in many models.
Is that possible to create a class in vb.net that is not in the default namespace of the project?
for example, say you have a project call sample1, then automatially IDE will have everything default to the Sample1 as your namespace root rather than under global, which is find for most case.but I want to create some classes that is directly under global namespace
I've just picked up a project from someone who has recently left our company, and the project file for the project has somehow had XML documentation deactivated. Typing ''' no longer automatically creates XML documentation segments, and existing XML documentation within the code does not show up in Intellisense, and is also not correctly highlighted as XML documentation.
In addition, the Intellisense for the My. namespace contains only MySettings, Resources and Setting under the "All" tab. Everything else is missing. Attempting to manually write My. namespace code results in compile errors. These are not problems with the IDE; I can start a new project and both Intellisense and My. work fine in these new projects. I can only assume that this is something which has been set on the project itself.
how can I import the System.ServiceProcess namespace into a WPF project in VB.net (not C#)? The ServiceController object is not in the toolbox in VS2008 and can't see to figure it out. Any ideas? If that particular namespace cannot be imported into WPF projects, could somebody suggest another way of controlling windows services from a WPF application? I know this framework is focused more on multimedia apps, but would really like to switch over some of my tools to WPF.
How does one gain programatic access to the information that is entered into the "My Project" properties Application section?I am able to pick up the assembly name from those properties, but I haven't been able to pick these up.Below is the line of code that makes me interested in picking this up programatically. I have found that if the name within the quotes for Sections (GenConfig) doesn't match exactly what is entered in those properties, I will get an application error during run time.How do I reference that property?Is there a better way to pick that value up?
Dim applicationSettingsSection As ClientSettingsSection = config.SectionGroups("applicationSettings").Sections("GenConfig.My.MySettings")
I am working on a solution that does not name namespaces in code files. Instead it uses the root name space of the project (which is the same across all assemblies). Basically there is only one implicit namespace.
Well, I am trying to isolate some code so that I can run FxCop against it. I explicated named the code file with a namespace to do this. This works for FxCop, but it bricks the entire solution.Visual Studio is now asking me to prefix all uses of the implicit namespace with Global. So instead of:
I use Excel PIA thru "Imports Excel = Microsoft.Office.Interop.Excel". IDE allows to set "global" reference for any namespace (in Project -> 'Project name' Properties -> References). But it doesn't allow to set alias for this namespace, so I have to write "Imports Excel = ..." thru all files where I need it. This would be great to have such thing in IDE!
Public Class aaMyForm Inherits Windows.Forms.Form Added some controls. Build it, add the .DLL as reference to my other project.
In my other project: Imports MyLib Public Class XForm Inherits aaMyForm
The events from aaMyForm execute correctly but the controls added to it are not shown on XForm. I have found some info about set Modifiers Protected in order to be able to change the functionality of the controls but havent found anything about why the controls aren display on the XForm.
I have received a project from other developer. This project as serveral references which are alright.There is only one reference that is not good.It's the Microsoft visual basic PowerPacks. I have the dll in the place where the other ddls are but still the project says that it can not find the reference specified.The DLL name is: Microsoft.VisualBasic.PowerPacks.dll it's on the path: C:Documents and SettingspribeiroAmbiente de trabalhoSGLCBuild I have other dlls there that are with the right references on the project...
