wrong referenced assembly version (using VS 2008)

I just copied an existing project to  new machine to start developing on it
The project originally referenced an older version of the assembly ( v1.0.0.0- My new machine has the latest version( Using MS VS 2008

Plz find the my  web.config code

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
				<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
				<bindingRedirect oldVersion="" newVersion=""/></dependentAssembly>
				<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
				<bindingRedirect oldVersion="" newVersion=""/></dependentAssembly></assemblyBinding></runtime></configuration>

Open in new window

How to set output path and assembly name properties appropriately explain me in detail i am  new  to .net and all.
prashanth agsoftware engineer Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Tushar ParekhIntegration Project of Major Payment Gateways into a Single Payment Gateway Switching SystemCommented:
You can go ahead and execute  gacutil /l  on VS 2008 Command Prompt where the GAC shows all the details of the assembly.


C:\> gactutil /l


Check that you are referencing the right assembly version

STEP 3 :

Check for dependent assemblies and see if they are properly referenced in your local project and the GAC.

This can be checked by Removing the reference from the local project and compiling and checking whether the project
is dependent on that assembly.

STEP 4 :

Check Assembly Info of the DLL by going into Add Reference ... and selecting the right version assembly and Public token. Once you reference it in your local project , two things

1. If Add Reference has included the right assembly it will compile.
2. If it does not compile then you need to Check using Steps 1,2,3 and insert the entry into web.config for the dependant assembly in the assemblies section.

STEP 5 :

Check that you are referencing  in your code using the "using" clause;

I think the above checks will ensure that you are using the right assembly version so that your program can compile.

STEP 6 ;
You can try by downgrading the Framework version, Copying the old assembly into your old project and try compiling it.
It may work as this has been tried and it has worked.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
prashanth agsoftware engineer Author Commented:
gacutil is not recognized as an internal or external command, operable program or batch file.
Jacques Bourgeois (James Burger)PresidentCommented:
Use the Command Prompt that is available with the Visual Studio tools in your Windows Startup menu (if you have one) or your Visual Studio tiles group (Windows 8). It is set so that you can call any of the command line tools without having to know where they are on your computer.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.