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 ?
I develop an application through two multi project solutions.There is one solution for the data layer stuff and another one for the front end stuff.All the dlls are referenced in a startup project and have copy local = true. So the build output from the GUI solution and the dlls referenced from the data layer solution should be copied to this startup project's bin folder. This seemed to work without issue for some time, but after changing source control, after a rebuild of the data layer solution, I clean the GUI solution and get the following output: [code] I have researched this problem and it seems microsoft are aware of a problem, logged under MSB3061... but no solutions have been posted by MS. Several users have suggested stopping the indexing service from indexing bin and obj folders (I've done this). I've also ensured that none of the bin/obj folders are under source control. I downloaded FileMon from sysinternals and it says that devenv (GUI) has the file locks.
I have developed a couple of windows applications in Visual Vasic Express 2008. To my horror, I have just discoved that the Setup Project is not available in the express edition.I have been searching to discover which DLLs I will need to include when using my 3rd party Deployment Application.
I know which ones I need for my 3rd Party Controls, but am stuck on which Microsoft DLLs will be needed the Microsoft Controls I have used, plus any other Common DLLs that are always needed.
I have tried searching Microsoft's site but without success.
Under VB.Net 2005, I created a Setup Project which produced installation files for a windows application. I placed the mdb file in the User's Application Data Folder and remapped the DataDirectory to Environment.SpecialFolder.ApplicationData at runtime. Unfortunately, sometimes the system just did create the mdb file at the Application Directory.
An example was that I installed the program in Windows 7 under a normal user account. I chose inside the installer that the program would be made available to everyone. After installation, the mdb file would be created automatically for the Administrator account but not for the normal user account. For XP, the whole thing worked fine. I am tempted to write a routine to check and create the mdb file if it is not present, but why does this happens and what other opinions do I have?
I created a standard exe project and then an Activex exe.I compiled the activex exe and tried to make a project reference to the activex exe and keep getting the error ... can not be referenced because its project type is exe
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.
As per [URL] How can I achieve this? 'processPacketVB' is a 'variable' but is used like a 'method' is the error I'm getting with these references to the project and class and function.
using VBProcessPacket; namespace UIST { public partial class FormActionMenu : Form { private void timerDelay_Tick(object sender, EventArgs e) { VBProcessPacket.ProcessRX processPacketVB = new VBProcessPacket.ProcessRX(); //read the receive buffer as a string RXpacket = processPacketVB("test"); // processPacketVB throws the error 'processPacketVB' is a 'variable' but is used like a 'method'
I have a project which contains all custom controls and images; we'll call it projectBase.Now I have created a windows forms project (project1) that references projectBase. I need to access the embedded resource (images) of projectBase in project
I want to create a real setup project for my application so when someone want to download it he can run only setup, not default setup that provide me VB . How can I do that?
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:
Is it possible to access the My.Settings of an other DLL referenced in the current Project? I have a Database project in which Settings the ConnectionString is stored. I need access to this Setting in an other Project(for Log-File).
Everything was fine but suddenly appeared this error when I built a project. Warning 1 The referenced component 'stdole3' could not be found. Warning 2 The referenced component 'stdole2' could not be found. [URL]
I am trying to instantiate a c# class whose project is referenced within a vb.net project.By providing the following declaration/instantiation of the class, I hoped to be able to access the instantiated classes publicly declared byte array within a vb.net module.The compiler won't let me. I get the message Access of shared member, constant member, enum member or nested type through an instance; qualifying expression will not be evaluated. It wants me to replace the reference to the instantiated class and public member frameData() with the general Class definition name. Why can't I access frameData through the instantiated variable rxFrame?
When I try to compile my VB.NET web project, I get an error that reads:[PropertyName] is not a member of '[Namespace.Class]'The class referenced is part of a dll that the project references. The property definitely exists in the referenced class, and its access modifier is Public. What's more, if I update the reference, or just remove it and add it back, the error goes away: the intellisense shows my property -- all is fine.. that is until I try to compile again. Then the error returns. I've even restarted Visual Studio to no avail. What is going on?[UPDATE]After Will's comment, I've changed the namespace to something I am absolutely sure is unique. Now, I am getting more compiler errors of the same genre. The compiler is not recognizing some of the overloads although they are right there in intellisense. Weird!
Dim gis = New MapQuestGeocoder Dim r = gis.GetResult(address) originCoord = r.Coordinate
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've finally got a project compiled and tested and ready to roll out.I have discovered that the "Publish" option is not what it seems, and that we must create a separate "Setup Project" to carry out the task of installing the files.This is not the most intuitive process I've seen, and the online help on that subject is not easy to understand.I was hoping that someone could direct me to a tutorial or guide that would step me through the specific approach I need. Many of the other guides online are vague and address multiple scenarios and do not separate the approaches very well.I have the contents of my project in /bin/release. It runs nicely by iteself with no errors.Here's what I need:
1. To create a setup exe that I can distribute that will install my software, with all of the supporting (resource) files and folders. 2. I need the setup process to force the installer to "agree" to a EULA. 3. I'd would like to provide an image on the installation screen/popup. 4. I would like the software registered in the registry and rely on it being there in the registry. 5. I need it to default to program filesprojectname (it does by default)
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 new to this Forum and relatively new to VB programming. I have read some really good posts here and thought I would ask about a perplexing problem I'm having. I createdindows Form application, built it and deployed it with no problems. However, when I added a small block of code, re-built the app and went to add the app to the Project Output Group in the file system editor the project was not in the Project drop down list. I closed the Setup project and deleted it from the project folder and checked my code and re-built the app and tried the Set Up project again with the same result
I got warnings on my project, does somebody know how to reference this assembly. this is probably because the project has these crm.mytextbox type textboxes and other controls instead of normal system.windows.forms.textbox.Warning1Could not find type 'crm.Mycombox'. 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.00
I am reinitiating again with these great topis on .Net. Mainly VB.Net. A friend of mine shared source projects, but can not compile. It is composed of a project that creates an .exe file and more than one project that create a DLL that are been used during the program execution. The thing is that project 1 (that creates DLL1) has a reference to DLL2. Normal I would say. But what surprised me is that project 2 (that creates DLL2) has a reference to DLL1.
More complex? Let's say that the program has 6 different projects (that creates 6 DLLs) and each of those has a reference to the others and viceversa? DLL1 has a reference to DLL2, DLL3, DLL4, DLL5 & DLL6. DLL2 has a reference to DLL1, DLL3, DLL4, DLL5 & DLL6. DLL3 has a reference to DLL1,..... and on and on. How to compile successfully these DLLs?
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.
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.
Ok, imagine the simplest solution in Visual Studio 2008 with framework 3.5 (OS = Win XP) where I have added a class library. Then I've added a COM Class. This COM Class is so simple, it only exposes 1 function:
Public Function SayHello() As String Return " Hello." End Function
