Unfortunately I cant send you sample code because now viewer and annotation embeded in
our project and i cant send it. But if you want to see i can show you with team viewer. But same dll’s works fine on my developer machine, there is no mismatch with those two dlls. I have create two virtual machines for this, both gives same error.
Yes MVC is locally installed on my machine, but its not installed my virtuals so i create a test console project and i add mvc dlls from nuget. After build i get all dlls from test project but it didnt solve the problem its want to System.Web.Mvc 3.0.
Actually on my first try i did it like this;
It wanted System.Web.Mvc 3.0, then i go to my GAC folder and i take it from there and put the dll to virtual.
Then it wanted System.Web.WebPages.Razor, after that it wanted System.Web.WebPages, after that it wanted System.Web.Mvc 3.0. Thats why i think it wants one of its depencies, then i create test project and get all dlls from there. But i didnt solve the problem.
My current problem is MVC dll. But my actual problem is i build project with viewer version 126.96.36.199626, why it wants to 188.8.131.5222. Also, I set it “do not use specific version” from reference options, so it have to dont look dlls versions. But it needs to specific version.
Thank you for information, I’ll be wating next release.
My concern is, after we start install new version of our project license file will be in their servers and if they discover how to use it-If they realize its a license file, they can easyly learn how to use it from documentation- They can use it, its loyality free. We dont want to use it, for now i’ll change license file name like “somethink.dll” or somethink like that before new release, they wont touch it. Aspose is your partner i suppose so, license management like aspose can be better. Its only my opinion, you know better it than me.