I have just updated the PostSharp to PostSharp 3.1 [3.1.41.0, 32 bit, CLR 4.5, Release] and am getting this error. How to fix this?
Fixed in version 3.1.42: PostSharp failed with code: 4
Related
I can debug on MyMac (Mac Catalyst) no problem but not on the simulator, I get the following errors in the Application Output:
xcodebuild[4480:64944] Writing error result bundle to /var/folders/wh/z7x5swm90fb6f6cxfp39760h0000gn/T/ResultBundle_2022-30-10_10-46-0020.xcresult
xcodebuild: error: SDK "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk" cannot be located.
xcrun: error: sh -c '/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -find simctl 2> /dev/null' failed with exit code 16384: (null) (errno=Invalid argument)
xcrun: error: unable to find utility "simctl", not a developer tool or in PATH
I'm using VS17.4 (preview 5 I think, how do I check? It just says 17.4 build 2339) and Xcode 14 for the iOS 16 SDK. I've checked in Preferences > SDK Locations > Apple and everything looks as it should... I'm a Mac noob so is there just a setting I'm missing somewhere?
If I try to build the release for publish like so VisualStudio crashes!
dotnet publish -f:net7.0-ios -c:Release
Update:
I just dropped back to net6.0 and am getting the same error. I didn't have Xamarin.Mac installed but installing it made no difference.
Below are some more component details of VS:
Xamarin.iOS Version: 16.0.0.72 (Visual Studio Community)
Xcode 14.0.1 (21336)
Xamarin.Mac Version: 8.12.0.2 (Visual Studio Community)
I can also see that the directory referenced does exist, or is it not supposed to look like that?
I had two version of Xcode installed which seems to have confused things. Uninstalling both then reinstalling 14 has fixed the issue.
I just installed Visual Studio Code and the DotNET Core SDK on a fresh Windows 10 32-Bit machine. However, I don't get it to run and to work properly.
I've loaded the csharp extension (Omnisharp) in Visual Studio Code. It is obvious that it seems to load x64 packages instead of x86:
[INFO] Starting OmniSharp at 'd:\Entwicklung\MyFirstApp'...
[INFO] Installing to C:\Users\Daniel\.vscode\extensions\ms-vscode.csharp-1.1.5\.omnisharp
[INFO] Attempting to download omnisharp-1.9-beta5-win-x64-net451.zip...
[INFO] Downloading to C:\Users\Daniel\AppData\Local\Temp\tmp-1252lY4HMeX6qNhB.tmp...
This leads to the error that the Debugger cannot be installed:
Error: Can not find runtime target for framework '.NETStandardApp,Version=v1.5' compatible with one of the target runtimes: 'win10-x86, win81-x86, win8-x86, win7-x86'. Possible causes:
1. The project has not been restored or restore failed - run `dotnet restore`
2. The project does not list one of 'win10-x86, win81-x86, win8-x86, win7-x86' in the 'runtimes' section.
Error:
System.InvalidOperationException: Can not find runtime target for framework '.NETStandardApp,Version=v1.5' compatible with one of the target runtimes: 'win10-x86, win81-x86, win8-x86, win7-x86'. Possible causes:
1. The project has not been restored or restore failed - run `dotnet restore`
2. The project does not list one of 'win10-x86, win81-x86, win8-x86, win7-x86' in the 'runtimes' section.
at....
How to fix this?
Thanks!
I have a netbook that I was hoping to use with Windows 7 32 bit and VSCode / Omnisharp and I have hit that wall as well.
Omnisharp only supports 64 bit at the moment. There is no known plan for a 32 bit version.
What is confusing is that it USED to be 32 bit compatible! Either make the switch to 64 bit (if your hardware allows it) or set up a different tool chain (perhaps using SharpDevelop?).
People have already requested this change but the devs don't seem to take it seriously.
I'm running Eclipse with RoboVM plugin and I wanted to try IOSDemo sample project described on robovm.org (http://www.robovm.org/docs.html). When creating the project in Eclipse and running it I got following error message.
An internal error occurred during: "Launching IOSDemo".
java.lang.IllegalAccessError: tried to access method java.lang.Object.clone()Ljava/lang/Object; from class soot.toolkits.scalar.LocalSplitter
I found out that it's related to JDK version (I'm running JDK 8.0 ea, build 112). When running on JDK 1.7.0_45 and building the project on cmd line it builds and runs OK.
Is it known problem, is there any workaround or fix? Thanks
This is most probably due to a bug [1] in the recent early access builds of Java8. It looks like the bug was resolved a few days ago but as far as I can see the fix didn't make it into the b113 build. Please use the latest Java7 release or an earlier Java8 EA build until a Java8 build is available with this fix included.
[1] https://bugs.openjdk.java.net/browse/JDK-8026394
In Xcode 4.4 I am getting error when I try to build iOS project that has methods written in assembly. I am getting error "Inline Assembly Issue - invalid operand for instruction" for this line vqrdmulh.s16 q2, q13.
I tried to compile with LLVM 4.0 and LLVM GCC 4.2 but I am getting the same error.
Project was compiling fine in previous version of Xcode.
Does someone know how to solve this error? Thanks.
I'm using FDT 3 enterprise with Flex 4.5 SDK on Mac OSX
Running works fine.
Debugging throws an internal error:
java.lang.NullPointerException
at com.powerflasher.fdt.core.launch.debug.concrete.FDBVersionTools.versionParts(FDBVersionTools.java:44)
at com.powerflasher.fdt.core.launch.debug.concrete.FDBVersionTools.compare(FDBVersionTools.java:19)
at com.powerflasher.fdt.core.launch.debug.concrete.FDBVersionTools.lessOrEqual(FDBVersionTools.java:7)
at com.powerflasher.fdt.core.launch.debug.concrete.FDBVersionTools.inRange(FDBVersionTools.java:54)
at com.powerflasher.fdt.internal.core.debugger.adapter.FlexSdkVersionTools.covers(FlexSdkVersionTools.java:25)
at com.powerflasher.fdt.internal.core.debugger.adapter.FDBAdapterLoader.cover(FDBAdapterLoader.java:51)
at com.powerflasher.fdt.internal.core.debugger.adapter.FlexDebuggerLoader.searchAdapterLoader(FlexDebuggerLoader.java:88)
at com.powerflasher.fdt.internal.core.debugger.adapter.FlexDebuggerLoader.loadDebugger(FlexDebuggerLoader.java:81)
at com.powerflasher.fdt.core.launch.DebugSessionManager.getDebuggerFor(DebugSessionManager.java:50)
at com.powerflasher.fdt.core.launch.DebugSessionManager.launchSessionFor(DebugSessionManager.java:106)
at com.powerflasher.fdt.core.launch.DebugSessionManager.launchSessionAndKillOld(DebugSessionManager.java:146)
at com.powerflasher.fdt.ui.launch.StartDebuggerTestLaunchConfigurationDelegate.startDebugger(StartDebuggerTestLaunchConfigurationDelegate.java:36)
at com.powerflasher.fdt.internal.ui.launch.fcsh.MxmlcLaunchConfigurationDelegate.startDebugger(MxmlcLaunchConfigurationDelegate.java:348)
at com.powerflasher.fdt.internal.ui.launch.fcsh.AbstractFCSHLaunchConfigurationDelegate.launch(AbstractFCSHLaunchConfigurationDelegate.java:174)
at com.powerflasher.fdt.internal.ui.launch.fcsh.MxmlcLaunchConfigurationDelegate.launch(MxmlcLaunchConfigurationDelegate.java:237)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:866)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1069)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
I'm not using any uncommon debug/compiler-arguments
Has anyone seen this before?
The Flex Debugger API changed quite a bit from Flex 3.X - 4.0. This means that your older FDT (version 3.x) is likely not compatible with later Flex SDKs. That is why you are getting that error.
You'll need to upgrade to 5.5 (or FDT 4.5 if you have a FDT 4 license)b/c the FDT team has had to rewrite parts of the debugger to make it compatible with Flex 4.5+. We've done our best to keep the upgrade price minimal.
http://fdt.powerflasher.com/buy-download/