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?
they need to make some compare version between host version and client version.. and each 1 version different will download the file to the client..[URL]..with both example, how can i make a program in VB.NET just like i said just now?
I have a XML file with the latest application version number, I have this loaded into a variable, how can i compare this against the application.info.version to see if it's the latest version??
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
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.
I 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.
I have problem when i use DTS package in my Application which I use VB.net .when i install the Application in the client and run it the are message appear :" could not load file or assembly ' interop.DTS,version=2.0.0.0,cultral,publickeytoken=null'or one of its dependencies . the system cannot find the file specified " In my PC run successfuly but in the client the previous?
I 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..
How 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.
VS 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:
I'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:
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)
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.
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.
I 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 ?
I'm working on a program that set up as master/details. I'm working on making save checks in the program, so that if something gets changed, it gives a warning when leaving the form if it hasn't been saved. I've got it mostly working, but I'm having problems with when i get to my details section.
The details section is a DataGridView (DGV) that loads with a one to many relationship. I've got is set up right now that when the form loads, it takes and makes an array call aryOriginals, and as you close the form, it makes another array called aryClosing. It compares these two sets of arrays, and if nothing is different since the page opened, it will close without any problems. If it has been changed, a msgbox pops up to let the user know that there has been a change since they last saved and asks if they want to wait to close the form so they can save.
All of that is working great. What I'm having a problem with is doing the same thing with the datagridview. And before anyone suggests it, I can't use DataSet1.HasChanges, because that was giving me weird problems of saying there were changes when nothing changed due to a custom made combobox i use in a few of my datagridviews. So I need some way of comparing the two datagridviews. I've looked online, but can't seem to find anything with what I'm looking for.
Visual Studio 2010 Pro SP1, SQL Sever 2008 R2, Vb.Net coding
Is there any way to make my programs use a lower version of net.framework other than the newest version 4 that comes with VS2010?I use my programs within a closed network and there isn't an easy way for me to install any software since I'm not the administrator.
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]
Every 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
I'm trying to add functionality to my application that will disable buttons and checkboxes depending on what version the OS is when the app is launched. I made a test app to test this but unfortunately I can not get it to work. Here is my code:
'OS Check Dim osValue As Object osValue = My.Computer.Registry.GetValue("HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrent Version", "CurrentVersion", "5.2")
[Code]...
*Note - 5.2 is Windows 2003, 6.0 is Vista, 5.1 is Windows XP
I have created a license system for my application with MySql about half a year ago. What it would do is take the serial number and send it to my server if the key was correct it would return a 0 if its wrong the return value would be a 1.The problem was that when the serial number was entered correctly my program would create a "fake file" for example vb.dll in the system.And on run time my program would check for that vb.dll if the file exist it would skip my trial program and run the app as a full version. Half year later i think creating a "fake file" and checking for it on start up is extremely wrong and that's not very good security.How can i check the difference between a full version and unregistered version?
I am trying to upgrade a project from VS2005. It is a VB.NET project B that depends on a C# project that references a C++ dll, A.dll. I am getting an error saying 'Unable to find assembly A_class, Version 2.0.0.0, Culture=neutral, PublicKeyToken=null'. The targeted platform of the C++ project is 4.0 and since that project depends on others, I can't downgrade it. But I did set the platform for the VB.NET project to 4.0. What else does the Version 2.0.0.0 refer to ? I have tried to create a brand-new project and added the vb forms into it after I have built it successfully. The C++ dll is in the output directory, if the VB project doesn't find it there, it doesn't get to this point. During build. I either get no error (but forms don't load) or I get 2 errors (one for each form):
I have a simple application, that was working just fine then all of the sudden I open the file and the design pages will not show up and I get the following warnings:
Warning 1 Could not load type 'System.Object' from assembly 'mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' because the parent does not exist. G:ProgramsCONNS v 1.0ConnectionsFrontPage.Designer.vb 149 0