After installing latest Glass Mapper I am seeing this issue:
Could not load type 'Glass.Mapper.IDependencyResolver' from assembly 'Glass.Mapper, Version=4.2.1.188, Culture=neutral, PublicKeyToken=null'.
Sitecore Version : Sitecore.NET 8.1 (rev. 160519)
Glass Mapper : Glass.Mapper.Sc
Yes before installation the project had references to Sitecore.Kernel and Sitecore.Mvc dlls.
Did anyone encounter this issue before?
After banging my head finally I found out the reason... In the project there was an old glass mapper v3 or below was installed & uninstalled which didn't complete all the way through. It deleted all the references from the project but it didn't delete all the config files. It left glass.config in the app config folder and the include folder. After deleting these two files it started working as expected.
Related
I'm following a tutorial to create a cross-platform app using xamarin.forms
except that I'm using Windows 7 and hence I skipped those steps for UWP part.
Now when I trying to build the solution, I'm getting the below error message
1> No way to resolve conflict between "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" and "mscorlib, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e". Choosing "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" arbitrarily.
Based on findings on the net it seems that something to do with versioning messed up however this should not happen as it's a new solution from scratch.
I've also checked the properties that stated as below:
- "Compile using android version (Android 7.1(Nougat))"
- Android Manifest "Target Android version" Use compile using SDK version
Well to be exact, the build was successful but with error logging as output. Please refer to below image
May I know what else I can try?
You can fix this by issuing an update-package -reinstall command in the Package Manager Console.
Make sure that your Xamarin (Visual Studio) installation version is the same as the Xamarin NuGet packages your using.
I recommend to:
Update Xamarin and your Xamarin NuGet packages to the latest versions.
Clean (in build menu)
Rebuild (in build menu)
Try again, if it does not work, continue steps:
Update all your Android related installations (using the SDK manager)
Check the paths for JDK, SDK and NDK in Visual Studio => Options => Xamarin
Try again
It could also be, that you are using a third-party NuGet package that is not compatible with your installed versions. Try removing NuGet packages to isolate the problem.
Unfortunately, there could be many things wrong here, but mostly it is related to versions and installations. Hope this helps.
It looks like you're trying to deploy to a device that does not meet the target requirements.
Verify that the version of the device or emulator you're working on is at least what is shown in your Android Build Options.
To troubleshoot any issues, I'd recommend opening the Android SDK Manager and downloading the Build and SDK tools that match the device you're planning to test on, and rebuild your project targeting the new SDK.
After installing latest update for VS2017, I lost almost all the project templates for starting new project. I get following message when starting new project.
I uninstalled and then reinstalled some “Workloads” using new installer without success.
After searching web for solution, I tried to install “NuGet Package Manager” using Extension manager, but seems there is no NuGet Package Manager for VS2017.
Any jugar/solution please?
Repairing VS2017 solved the problem. Is it not a very long route?
I have installed VS 2012 Ultimate and Sitecore Rocks 1.4, connected to the sitecore instance, create a solution and connected with sitecore rocks and when I try to create a layout from my solution Im getting an error
"Could not load file or assembly sitecore.rocks, version 2.0.0.0, culture=neutral, publickeytocken="...
I tried to installed Rocks version 2 but its not getting installed in VS 2012,
Please help me on fixing this..
I know this is an old question but I hope this will help someone in the future.
I was having the same error and then I realized the extention is local to the user. I login as a different user and install the extention and it worked for that user.
So under my user I uninstalled the extension.
Remove folder C:\Users\ {Your Username}\AppData\Local\Sitecore
Then searched for "rocks" in C:\Users\ {Your Username}\AppData\Local\Microsoft\VisualStudio and add remove those items too.
I don't know if I had to but I also removed these registry entries.(Remember to do a backup before removing them.)
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\ {Your VS version}\DialogPage\Sitecore.VisualStudio.Options.VisualStudioOptions
HKEY_CURRENT_USER\Software\Sitecore\Sitecore.Rocks.VisualStudio
HKEY_CURRENT_USER\Software\Sitecore\VisualStudio
HKEY_CURRENT_USER\Software\Sitecore A/S\Sitecore Rocks
Rebooted and reinstalled the extension then everything worked.
I'm using Visual Studio 2015 community along with some other in our team. A mvc web application that I created works fine on my machine but when others get it to build, all packages download successfully but some of the core MVC such as Microsoft.AspNet.Mvc, Razor, etc don't install.
What was weird that on their machine, if they went into PM and downgraded the MVC package to 5.2.2 and then upgraded back to 5.2.3 it worked. But now when setting up the build on our build server, we get the same issue!
Any ideas why this bizarre behavior?
Didn't check that but why would that matter? When the Dev downgrades the version on 1 package and then upgrades back everything is as it should be
EDIT (4th Oct 2016) after investigating a bunch of things:
One of the developers at one point committed the "Packages" folder which sits at the root which had the "Microsoft.AspNet.Mvc" and other folders but without the dlls. This made the "Restore packages" not really "Restore" these as the folder already existed but when the build was run the artifacts weren't actually there in the folder to be moved into bin.
I deleted the packages folder, added it to gitignore and committed the change which made everything 'green'!
I have an outlook 2010 add-in that has a service reference to a simple web service we have set up.
The config for the service is in the app.config file.
This add-in is deployed using windows installer into the program files folder.
This has been working without a problem until yesterday.
Yesterday I installed VS 2010 SP1 and now when the add-in tries to access the web service it has the error "Could not find default endpoint element that references contract in the ServiceModel client configuration section."
Does anyone know what has changed and what is causing this problem?
If I open the project in VS, build and then run from within VS the config is picked up fine.
Thanks
Gavin
The actual solution is more simple. There was a breaking change made to VSTO 4 sp1 in that the manifest has to be a fully qualified URI. So when building your setup project, you must prefix the path to the manifest with file:/// and everything works as you'd expect again. They didn't get the documentation and tutorial pages updated in time for the release. I'm not sure that they have been yet.
Perhaps you're hitting a problem with extensionless services after installing SP1? http://support.microsoft.com/kb/2468871 - Issue 16?
I had this exact same problem. After installing Visual Studio sp1 (which installs VSTO 4 sp1), my Outlook addin could no longer find its config file for service endpoints. The only solution I've found so far is to run the VSTO setup (the new one) and choose uninstall, then run the old version that was previously installed and rebuild the setup package. If the new version is installed on the client machine, that machine will have this issue. Your setup may not detect it because typically you specify a minimum version for it to look for. I haven't found any other info about others having this problem besides yourself or anything official from MS about the problem.