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:
AssemblyVersion("1.0.0.0")>
How 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 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 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 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)
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 RepliesI 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 ?
Getting 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 work with VB.NET 2005 and I want to set the application EXE name according to a certain condition. For example:
I have a variable its name Version
If Version = 1 EXE name will be CarsApp
Else If Version = 2 EXE name will be BuildingApp
and so on.
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 RepliesI've got a simple VB.Net 4 WinForms application that does basic code generation. The code generation creates a DLL assembly perfectly fine, but each time the DLL is generated it needs to be registered programmatically with the GAC. The reason it must be registered is that it is a COM object that when deployed gets called via CreateObject from a VB6 application. Eww, I know.All of this works fine: the DLL generation, registering programmatically and using the generated DLL from the VB6 application.The problem is that my application that does the code generation can only generate the DLL once before the DLL is locked out by the process with no way to unlock it without stopping the EXE and starting it up again. This obviously prevents the user of the code generation tool from making a change and recompiling the DLL without restarting the application.[code]
I've tried throwing the assembly definition into a different AppDomain as I've seen in a number of articles on the web, but none of the implementations that I've come up with has worked. In fact, nearly all of them ended up with the generated assembly then being defined in BOTH of the AppDomains. I've also tried doing a ReflectionOnly assembly load but in order to the the register functions the assembly must be loaded in active mode not reflection mode.[code]
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.
[Code]...
How do I programmatically increment a given version's number to the next version of the highest one?
For example if I have a file Program.exe with the following version numbers :
Program.exe 1.0.0.0
Program.exe 1.0.0.4
Program.exe 1.1.0.76
Program.exe 1.0.0.66
The next version number in this case would be 1.1.0.77
What's the easiest way to implement that?
Does anyone know of a way to programmatically determine which version of the .NET framework is installed on a computer? I was thinking of trying to scan the registry, but my main worry is that a user would need admin rights if trying to use the method
View 8 RepliesYou can get the version of your application sing My.Application.Info.Version. Is it also possible to set this version using code? This because I have a webservice that connects to a database and retrieves a version number.My application then compares that version number with his one, if it's old.. then it will download new files and change his version number.
View 3 RepliesI 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?
View 1 RepliesI 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):
View 1 RepliesHow to programmatically detect 32-bit or 64-bit visio version is installed?
View 7 RepliesI am dynamically generating a word file, and clicking the link opens the file save dialog and it says the document is a: Microsoft Word 97 - 2003 Document.What would I need to do to programmatically generate a 2007, 2010 word document.
Code behind:
Public Sub Page_Load(ByVal sender As Object, ByVal e As EventArgs) Handles Me.Load
'build the content for the dynamic Word document
'in HTML alongwith some Office specific style properties.
[code]...
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
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.