when I build I get this warning "Found conflicts between different versions of the same dependent assembly"the target for the application is any cpuI went through all refernced project/solutions - they are all any cpu, .net 3.5. There are some externally supplied dll from microsoft, sybase which I don't have control.
View 1 RepliesWhat's the meaning of this error? The first version the I had installed is the vb. 2008 express edition. Now I try to used the vb.net2008 team system. Is there any conflict with those versions that I had installed to my pc?
View 3 RepliesVS2008 / XP Pro sp3 / .NET 3.5 I develop during the day on my office computer and bring home projects on a laptop to work on over the weekend. After working at home then at work, I have a conflict that I don't understand. When I build, all is normal but when I debug, I get "Found conflicts between different versions of the same dependent assembly." If I click on the warning message I also get "Do you want to fix these conflicts by adding binding redirect records in the app.config file"?Both computers have same O/S, same SP, same .NET, same VS. Only thing that could be different is particular O/S updates that have been installed on each machine. What causes this warning and where do I look for differences? I really hate to let mSoft keep changing my code every Saturday and Monday. I just don't trust it on Mondays.
View 7 RepliesHow they relate and differ from each? What are the best practices for version control? Is there a primer about publish online? Or a good book?
And is it possible to make ClickOnce and a msi in one solution of VS 2008? If so, is there any conflict or pitfall?
BTW I am using VB if that makes any difference.
I have developed an application in VB.net which uses R Programming language. The library that help connect VB.net to R is called R-DCOM. The application requires the user to install R-Programming language into the user's computer. The application was working all fine until there was a version change in the R-Programming language. The specific libraries involved with this are: Interop.STATCONNECTORCLNTLib.dll, Interop.StatConnectorCommonLib.dll and Interop.STATCONNECTORSRVLib.dll. It also uses StatConnectorClnt.tlb, StatConnectorSrv.exe and StatConnLib.tlb to run the application. Is this something related to "DLL hell". Is there a fix to that I may not have to recompile and install the original code and install them to the user's computer all over again.
View 2 RepliesSimple question that does not seem to be covered: If I use a lot of Debug.WriteLine statements in my code, will they be completely absent in my production version?
I mean: Is the compiler smart enough to not emit any code for those calls? Or would I have to surround them by #if DEBUG..#end if directives?
I want my application to do something special :D.. jks
I just want it to compare assembly version to the file version something like this (btw i also want it if it is the same i want it to enable a button):
Private Sub StartSplash_Load(sender As System.Object, e As System.EventArgs) Handles MyBase.Load
If Assembly Version = File Version Then
[Code].....
so how do i detect Assembly & File version numbers?
I am debugging an assembly which I loaded dynamically with Assembly.Load(Byte[]), but I am facing some problems.First of all, I can't move the yellow arrow in Visual Studio 2010 to step into other lines of code, and also I am getiing exceptions ("Cannot find the method on the object instance.") when trying to do a quick watch on objects from a third party library (controls from Infragistics for example.)
Dim data = My.Computer.FileSystem.ReadAllBytes(file.FullName)
Assembly.Load(data)
When using Assembly.Load(String), everything works fine, and there are no problems.
Assembly.Load(IO.Path.GetFileNameWithoutExtension(file.Name))
EDIT: I tried loading the debugging symbols for my assembly with Assembly.Load(byte[]. byte[]), but it I sitll get Exceptions when trying to debug objects from third party libraries.
When an error occurs in any of my .NET assemblies the user just gets a generic error saying "MyApp has encountered a problem and needs to close. We are sorry for the inconvenience." I would like the user to to see the error message and line number if possible.From what I understand you need to deploy the pdb file along with your assembly. I did that, but it had no effect. This is a Windows application.
View 1 RepliesI have dll and exe files which have assebly version numbers different from the values stored in AssemblyInfo.vb.If I look at the information displayed in the Details tab of File properties in Windows, the File version and Product version values are identical with the values of AssemblyInfo.vb. But when I use My.Application.Info.Version to display the version number at runtime, the value displayed is incorrect. Also when I add a reference to a dll file, the referenced version is incorrect. The incorrect value is the same as the value last time AssemblyInfo.vb was edited on the local machine. If the AssemblyInfo.vb file is edited on another machine, the value won't be updated on other machines.
Typical example: On a nightly build the build server increments the build number of all AssemblyInfo.vb files. When developer workstations are updated in the morning (get latest) the build number isn't updated at runtime - even though the AssemblyInfo.vb file is updated and compiled into a new dll or exe file. But file properties in Windows displays the updated build number as described above. I've been looking for other places where a version number might be stored (in case there are more than one place to update the version number), but I can't find any reference to the displayed build number when I search the source files.
If a developer workstation edits the build number, compiles, and edits it back to the correct value and builds again, the displayed value at runtime is equal to the value in the source file. It's like the AssemblyInfo.vb files must be edited on the machine that builds the solution, or the result is not reliable..
I would like to get latest version of the assembly. how?
View 3 RepliesGet real assembly version? [code]...
View 8 RepliesHow does the Assembly Version get generated in VS/.NET? I know that there is a couple of strings in AssemblyInfo.cs or AssemblyInfo.vb with something like this:[code]But how does the final assembly version get created? How does it get incremented? Where does the last value get stored? We have a custom in-house release environment and I would like to customize the assembly version.
View 4 RepliesVS 2008 Is there a way to set the assembly version programmatically? For example, My.Application.Info.Version.Major is readonly. Therefore, I was wondering if there was a way to call some code from the assemblyInfo file to set <Assembly:
AssemblyVersion("1.0.0.0")>
I have developed an application in vb.net.I use a dll that I build as part of a different project in my solution. For some reason I don't get the full functionality of my application with the dll built as a "release" version, but it does work if the dll is built as a "debug" version (that's a whole different problem).I don't have a problem, for now, using the debug version.However, the problem I'm having is I am trying to deploy the application to another system and if I deploy the debug version of the dll I get a runtime error (see below).I have the .net Framework installed. I'm just wondering what has to be installed in order to allow me to use the debug version of the new system? [code]When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
View 1 RepliesI've seen a lot of the "auto version" update add-ons for VS, and well I decided to write one for myself. It's manually triggered, but put as a external tool in the IDE it works rather nice. I based it off of reading the AssemblyInfo.vb file for a project (so at the moment it only works in VB not C#). So my app (given certian parameters) will auto increment the FileVersion and Assembly version together, so they stay the same through out. (it simpler for me that way). But i noticed a little issue with this method of reading the assemblyinfo.vb file, changing the values and saving the file and then forcing a "Rebuild" of the project.
When I go to Explorer, right-click | Properties on the file, in the Version tab, the "AssemblyVersion" has not changed, where the Product and File Version has. so for example I've got Test.Exe I open up the project properties and set via the UI the versions to:
[Code]...
I am trying to use Ajax control toolkit in asp.net website. I copied the dll from one of my previous sample project. It has the following details
Assembly Version - 3.5.40412.0
File Version - 3.5.40412.2
Internal Name: Ajax Control Toolkit
Language : Neutral
Product Version - 3.5.40412.2
When I add reference to this assembly, it appears as "AjaxControlToolkit-3.5.40412.2" in the reference list. When I run the solution, I get a FileLoadException: Could not load file or assembly 'AjaxControlToolkit-3.5.40412.2' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
I created a vb dll using class library in visual studio 2010 [URL]... I have accessed this Dll in Excel VBA by referencing it through (Tools>>Reference)...I obtain different results when i run my program from Excel and when I run it from Visual Studio during debugging (here the debugging starts Excel as an external program). The results are exported by the dll function as a structure array ( The required values
are in double format in a constituent 1D array). The difference is as high as 5%.
What might have caused this difference? Could someone please help me with this?
I am having a strange issue when building assembly's for one of my modules.I was getting errors when running on 64bit which I traced back to being related to the assembly being 32bit specific. Our modules are(or should) all be built to be bit agnostic.Running CorFlags.exe on the assembly showed the following.
Version : v2.0.50727
CLR Header: 2.5
PE : PE32
[code].....
I want to get this Assembly version, I have an old application and lost the source code.
When I try to disassemble with reflect it ask for Microsoft.VisualBasic Version=7.0.3300.0 Where I can find it?
We have one program that acts as a "server" (so to speak) and many programs that reference it. every time we update the server, we are forced to update all the dependent programs to reference the new version number. Our IPC communication protocol is pretty stable and doesn't change, so we aren't worried about upgrade incompatibilities. I would like to know how to automatically reference the "latest" version of an assembly. What I mean is, if I choose Project->properties->references, I always get a specific version. Is there a way to reference whatever the latest version is? This way, we wouldn't have to update every program that is dependent on our server every single time there is an update.
View 1 RepliesI have this situation where LoadWithPartialName appears to be the only good alternative, although it is marked as Obsolete. I work in a very tight dev environment with versioning and deployment policies that cannot be easily changed or bypassed. Let's say there's a .NET executable that I have no control on (from another division). Let's call this the client AppA application. AppA's version is 10.11.12.x. Application AppA has a direct reference to one of our class library that provides some service to the caller (returns some information).
Let's call it SvcB and the version is also 10.11.12.x. Now, AppA's division does not need to update their system as often as we do, so AppA's version will stay 10.11.12.x for some time, probably until we decide to change the format of the class that is exchanged between us. Our division needs to change the logic behind the service SvcB more often and the version must change with every major deployement.
So let's say we change the logic and we deploy a new version of SvcB, 11.02.11.x. AppA will still reference the old version, so the logic being used is now incorrect. We are thinking of creating a new "facade" to our service. Let's call it SvcFrontB. SvcFrontB's version will stay the same, in sync with the AppA's own version. Now I need SvcFrontB to load the most recent version of SvcB through reflection. This way, I am sure the latest logic is always used. How do I achieve that without using LoadWithPartialName ?
How can i Auto update or manual update my Software version. when i build my project on debug mode. Software version only auto increment when i publish the software. but dont want to publish my software yet. my project is developing state.
View 1 RepliesGetting follwoing error while installing ClickOnce VB.net application"
"the application requires that assembly System.Net Version 3.5.0.0 be installed on GAC"
Is it possible to load a referenced assembly only if the .NET Framework version is lesser than a specific number? I'm using a selfmade LINQ library on .NET 2.0, but if the framework is 3.5+, it should use the M$ LINQ library, and ignore the selfmade one.
Here's my library: [URL]
I created one windows application in visual studio 2008 (.net 3.5) and successfully created setup application also. It working fine. But in the customer system the application throws the title error. I got from another thread as add 'stdole.dll' in the setup application. But that answer related to
View 5 RepliesEvery time I compile a new release build in vb.net 2009, the file version number of my main exe is correct, but the assembly version number is the same as the last build instead of the current version even though I manually change the file and assembly version in the design studio to be the same prior to compiling.The only way I can get the assembly version to be correct is to close Visual Studio and delete the obj folder. Then if I open the solution and recompile, all is well.
Here is the information copied from the About box in VS:
Microsoft Visual Studio 2008
Version 9.0.30729.1 SP
Microsoft .NET Framework
[code]....
I made an app that connects to a mysql database to update a table. It works fine from my test machine, but if i deploy the app to another computer I get error: Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'MySql.Data, Version=6.3.6.0 I'm going through google to find a solution, but nothing has stood out yet, just wondered if anyone has encountered this before and knows of a quick fix.
View 2 Repliesif you are debugging or releasing a projet , vs writes exe or bin files to the bin and obj folder in a release and debug version, are ther differences bewteen these files with the same name in 4 folders ?, eg myproject.exe
View 3 Repliesi create a simple webbrowser in a form , it works perfect on debug mode , but in release i always get this page cant not be displayed , no matter the website.
View 6 Replies