Last post Dec 20, 2007 02:17 PM by jcrabtreesla
Dec 17, 2007 04:42 PM|jcrabtreesla|LINK
I have 1 solution that contains many different projects. 1 of the projects is a Web Control Library. In the control library, I have created a web custom control. I built that project then added the custom control to my toolbox. I have been able to add the
control to the other projects (all AJAX web applications) in the solution just fine. The custom control will render in the design view perfectly. I was able to use the "View in Browser" option for a while and everything worked fine. But later I made some changes
to the custom control, then rebuilt that project. I right clicked on the custom control on each page and selected "Refresh", and all the changes were updated.
However, I am getting a compliation error (below) when I try to "View in Browser". It says the reference is to the wrong version. So, I removed the control from the page and deleted the reference in the References folder for that project. I then dragged
the control from the toolbox again onto the page. Same error. I can't figure out how to make it update the assembly version. I thought this should happen automatically. What am I doing wrong here? How can I fix this?
An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: BC32206: Indirect reference is being made to assembly AACCControlLibrary version 1.0.2907.20287, which contains 'ABCCMolecularDiagnosticsExam.form.CGIPersonalData1'. This Project references a prior version of AACCControlLibrary
version 1.0.2907.15673. To use 'ABCCMolecularDiagnosticsExam.form.CGIPersonalData1', you must replace the reference to AACCControlLibrary with version 1.0.2907.20287 or higher.
Dec 17, 2007 06:46 PM|cardona|LINK
when I was playing around with custom controls, every time I made changes and re-built it; On my test page, I would do what you did, but also remove it from the toolbox and add it again.
Dec 18, 2007 09:17 AM|jcrabtreesla|LINK
I just tried that and I am still getting the error. Also, I would think it shouldn't be this hard to update a custom control. It should be easy to update the control itself and have the control updated in the other pages, otherwise it's too time consuming
to even do a custom control.
Dec 18, 2007 09:36 PM|Nai-Dong Jin - MSFT|LINK
From your description, it should be a Broken References trouble shooting problem.
When you met the error “Indirect reference is being made to assembly <assemblyname> version <laterversionnumber>, which contains '<typename>' ”, to correct this error, you should:
Also, for these kinds of Broken References trouble shooting issue, there are some general solutions to handle that. See:
Dec 20, 2007 02:17 PM|jcrabtreesla|LINK
I tried to follow the steps you provided and the ones in the article, but with no results.
So, I just started playing around in the project properties. I ended up removing the reference path all together, then re-adding it, and it started working again. I don't know how/why that is any different than when I just deleted the reference from the
Reference folder, or why it wouldn't update the version without all that trouble.....hmmm confusing. But it works. Thanks.