First a GOOD ADVICE TO EVERY DEVELOPER, Test ASAP your proyect into UWP if you plan to go there, it will help you a LOT to see blown things away sooner than later…
After tearing 1/3 of a project apart for “incompatibility stuff thanks to Visual Studio” I managed to go to the 99% of the compilation process, just to thet a error and … wel… leave me in the middle air…
Can anyone have overcome this?
UnityException: Failed to run serialization weaver with command “Temp\StagingArea\Data\Managed\BugReportUtils.dll” “-pdb” “-verbose” “-unity-engine=Temp\StagingArea\Data\Managed\UnityEngine.CoreModule.dll” “Temp\StagingArea\TempSerializationWeaver” “-lock=UWP\project.lock.json” “-additionalAssemblyPath=C:\Program Files (x86)\Windows Kits\10\UnionMetadata\10.0.16299.0\Facade” “-additionalAssemblyPath=C:\Program Files (x86)\Windows Kits\10\References\10.0.16299.0\Windows.ApplicationModel.Calls.CallsVoipContract\2.0.0.0” "-additionalAssemblyPath=C:\Program Files (x86)\Windows
Is quite longer but you may get the idea… Anyone? Im disappointed and tired now…
Arcanebits
1- The error seems to be that Microsoft is NOT compatible with standard serialization, yes, im serious, try disabling saves and using basic playerprefs.
2- UWP Doesn NOT like DLL files. Just Dont
3- Do a couple of things, take you Set up to latest versions of all (SDK, Unityitslef. .Net 4 )
4- Do please, change from UWP, to D3D in the compilation settings, this will void the UWP itself that in my opinion its a badly implemented subset of D3D.
I don’t know what you mean by all of these, but what you wrote looks wrong.
UWP does support dll files just fine, as long as they are compiled for UWP (.NET for UWP is limited compared to desktop version). With il2cpp backend they should be fine though.
D3D has no effect here, scripting backend does.
Serialization weaver errors usually indicated issues with certain types, most commonly types that aren’t available in .NET for UWP. This is why I asked for complete error message.
Hi, Well my friend, that was my experiencie as you may see I did found a workaround since no answer or help was given in this forum since december last year…
You are the expert here, im just a noob talking nonses, please delete my coment.
@Arcanebits Not quite sure of your comments, did you find a work around? Sorry I didn’t follow your posts since December. Otherwise providing steps to reproduce on a minimum project would provide the best chance of receiving assistance. Personally I generally compile and test to a target platform on the first day of development to avoid such issues.
The 29 of Dec last year y posted “Anyone?”, second cry for help and nothing happened, this thread was revived by SonicViz who had the same issue, and I, responded to him what worked for me to overcome the issue, then Aurimas came to say my post was wrong and etc…
IMHO I just tried to help someone with the same issue, offer him what worked for my, but, and is a big one, Arimas already said my post was wrong.
Im not a UnityPro nor earn a dime here, I just tried to help, my bad I know nothing, like Jhon Snow, You are the pros, and for now on, I just will ask for help and obey, not try to help.