Explains a Visual Basic compiler bug where assembly version numbers do not update after rebuilding, affecting Workflow and other projects, and offers manual workaround steps.
If you are having an issue with the assembly version in your compiled assembly not updating after a rebuild then you are not alone. The is a bug in the Visual Basic compiler that causes this problem and it requires a manual fix:
http://kbalertz.com/952628/Assembly-Version-change-Visual-Basic-Workflow-projects.aspx
Not hard, but annoying…
To check the problem, double click on the assembly in your bin folder and open out the version tag.
You can see from the image below what I am getting at. This causes no end of problems with signed assemblies. The KBAlertz article above implies that this only affects Workflow assemblies. But I have has t6his problem in other types of Visual Basic project.
This is not a big problem unless you are creating custom assemblies for SharePoint and have a convoluted deployment process before you can test, and can’t figure out why you changes are not going through…
No related videos found.
If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.
We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.
Qualco
Genus Breeding Ltd
Cognizant Microsoft Business Group (MBG)
New Signature
Boxit Document Solutions
CR2
Boeing
Kongsberg Maritime
Akaditi
Milliman
Workday
Big Data for Humans
Graham & Brown
Capita Secure Information Solutions Ltd
ProgramUtvikling
Slicedbread
DFDS
NIT A/S
Department of Work and Pensions (UK)
Washington Department of Enterprise Services
Royal Air Force
Washington Department of Transport
Ghana Police Service
New Hampshire Supreme Court
Freadom
Trayport
Hubtel Ghana
Capita Secure Information Solutions Ltd
Milliman
Graham & Brown