For 2 days i have been fighting with this problem. and could not get a solution
link to my project files:
https://github.com/gitamsinghkaystha/streamingtestframework.git
ruby version:1.8
rubymine 4
Related
I have a MAUI project that references 3 .dll's that are built with netstandard2.1. I am working on a Mac with Ventura MacOS and Visual Studio 2022 17.4.2. I am having a problem building the .ipa for the iOS platform. I can compile all of the elements of the project but when I run the command
"dotnet publish -f:net6.0-ios -c:Release /p:ArchiveOnBuild=true -r:ios-arm64 --no-self-contained"
I get 3 errors all related to the .dll project files not referencing .net6.0-ios.
/usr/local/share/dotnet/sdk/6.0.404/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(267,5):
error NETSDK1005: Assets file
'/Users/davidrutter/Projects/RadixIQDealerPortal/aspnet-core/src/RadixDealerPortal.HttpApi.Client/obj/project.assets.json'
doesn't have a target for 'net6.0-ios'.
I've tried several things and searched all over trying to find a solution but without success. If anyone has an idea how to resolve this I would be truly appreciative.
You want to use the framework net6.0, net6.0-ios should not make a difference here as you are using --no-self-contained.
Leaving the options for net6.0-ios out should work too, as you already have the runtime defined.
TLDR;
remove -f:net6.0-ios
I am trying to get Xcode 10.2 to convert my hybrid Objective-C / Swift project to use Swift 5. Whenever I do this, however, the compilation files due to the following error
error: Multiple commands produce '/Users/<User>/Library/Developer/Xcode/DerivedData/SurgEval-chcbdqcuvbtwckedraqzdhwbsqpm/Build/Intermediates.noindex/SwiftMigration/SurgEval/Products/Debug-iphonesimulator/MYAPP.swiftmodule/x86_64.swiftmodule':
1) Target 'MYAPPTests' (project 'SurgEval'): Ditto /Users/alenox/Library/Developer/Xcode/DerivedData/SurgEval-chcbdqcuvbtwckedraqzdhwbsqpm/Build/Intermediates.noindex/SwiftMigration/SurgEval/Products/Debug-iphonesimulator/MYAPP.swiftmodule/x86_64.swiftmodule /Users/<User>/Library/Developer/Xcode/DerivedData/SurgEval-chcbdqcuvbtwckedraqzdhwbsqpm/Build/Intermediates.noindex/SwiftMigration/SurgEval/Intermediates.noindex/SurgEval.build/Debug-iphonesimulator/MYAPPTests.build/Objects-normal/x86_64/MYAPP.swiftmodule
2) Target 'SurgEval' (project 'SurgEval'): Ditto /Users/<User>/Library/Developer/Xcode/DerivedData/SurgEval-chcbdqcuvbtwckedraqzdhwbsqpm/Build/Intermediates.noindex/SwiftMigration/SurgEval/Products/Debug-iphonesimulator/MYAPPL.swiftmodule/x86_64.swiftmodule /Users/<User>/Library/Developer/Xcode/DerivedData/SurgEval-chcbdqcuvbtwckedraqzdhwbsqpm/Build/Intermediates.noindex/SwiftMigration/SurgEval/Intermediates.noindex/SurgEval.build/Debug-iphonesimulator/SurgEval.build/Objects-normal/x86_64/MYAPP.swiftmodule
I have already tried switching to using the 'Legacy Build System' as suggested in other similar questions, but I would like to migrate to the new build system.
I have also tried to change the product module name in my test target as suggested in another question, but that broke my tests.
The application and tests both build and run fine otherwise, I just get a compilation error while running the Swift 5 migration tool.
Any idea what's going on here, or some some docs I can look at to better understand this?
Thanks!
I was able to partly solve this issue by adjusting SWIFT_MODULE_NAME property in Test target.
My test's target SWIFT_MODULE_NAME was same as main target name, so i changed it
I have an Xcode project with unit tests. The product Tests.xctest is red. The unit tests build and run as debug versions. Why is it shown in red?
When I look into the products folder and drill down into the packages I see a unix executable Tests for the debug build but not for the release build. If I set it up in the scheme to build Test for release the build process fails saying failed to load module .
I'm thinking that it maybe is because the release version isn't building, but not sure why that is either. Why can't it find the module when I set both run and test to release? It builds and runs for release but tests won't build.
Ideas?
Update: I created a testapp and the problem persists:
It's a false error. Xcode has gotten this wrong for many years now.
http://docs.asp.net/en/latest/tutorials/your-first-mac-aspnet.html
Installed Node
Installed Yo
yo aspent
pick the web application
dnu update
dun build failed with spectacular 2400 odd errors
open the vsCode as we can issue a command on the top that did not work failed and complained omni sharp is not working.
dun went with beta version 1.0.0.4
some where i saw depends on mono downloaded mono installed it.
re-open VSCode and still fails to run with the following error message
error from the vscode
[INFO] Starting OmniSharp at '/Users/bvn/TestApplication'...
[INFO] Started OmniSharp from '/Users/bvn/Downloads/Visual Studio
Code.app/Contents/Resources/app/extensions/jrieken.vscode-omnisharp/bin/omnisharp'
with process id 2775...
[INFORMATION:OmniSharp.Startup] Omnisharp server running using stdio
at location '/Users/bvn/TestApplication' on host 2765.
[INFORMATION:OmniSharp.Dnx.DnxPaths] Using runtime
'/Users/bvn/.dnx/runtimes/dnx-mono.1.0.0-rc1-update1'.
[INFORMATION:OmniSharp.Dnx.DnxProjectSystem] Scanning
'/Users/bvn/TestApplication' for DNX projects
[INFORMATION:OmniSharp.Dnx.DnxProjectSystem] Found project
'/Users/bvn/TestApplication/project.json'.
[INFORMATION:OmniSharp.Dnx.DesignTimeHostManager] Listening on port
57325
[INFORMATION:OmniSharp.Dnx.DesignTimeHostManager] Process ID 2784
[ERROR:OmniSharp.Dnx.DesignTimeHostManager] Failed to launch
DesignTimeHost in a timely fashion.
[ERROR] Error: Failed to start OmniSharp
[INFORMATION:OmniSharp.Dnx.DesignTimeHostManager] Client accepted
127.0.0.1:57325
Here is how I manually installed OmniSharp into VS Code. I used the steps in this link to help point me in the right direction. After some tinkering, I got everything working in both OmniSharp within VS Code and the dotnet core debugger integration. The link above implicitly suggests putting files in the .bin\omnisharp\ folder (note the . prefixing bin) but, that didn't work... it worked when I put files in the bin\omnisharp\ folder.
I'm running Windows 10 64bit and .Net Core SDK/CLI v1.0.4 with VSCode v1.14.2. Here are the steps:
Install OmniSharp in VSCode and then close VSCode
If it does not already exist, create bin\omnisharp and .debugger folders under %userprofile%\.vscode\extensions\ms-vscode.csharp-1.11.0\
In the runtimeDependencies section of this packages.json, download the zip files for OmniSharp (.NET 4.6 / x64) and for .NET Core Debugger (Windows / x64)
Unzip omnisharp-win-x64-<version>.zip into %userprofile%\.vscode\extensions\ms-vscode.csharp-1.11.0\bin\omnisharp\
Unzip coreclr-debug-win7-x64.zip into %userprofile%\.vscode\extensions\ms-vscode.csharp-1.11.0\.debugger\
Launch VSCode and run thru a simple Hello World dotnet core example... everything should work.
I hope the info helps. :)
I have a NancyFX web project using SimpleAuthentication that works fine when self-hosting from the terminal. When I self-host from unit tests (NUnit runner with Xamarin Studio), I receive exception "Failed to reflect on the current domain's Assemblies while searching for plugin" with error message "Could not load file or assembly or one of its dependencies." repeated many times.
Any idea why this would fail? This looks like the code throwing the exception is at https://github.com/SimpleAuthentication/SimpleAuthentication/blob/master/Code/SimpleAuthentication.Core/ReflectionHelpers.cs. I tried a IntPtr.Size measurement to make sure they are running in the same 32/64 bitness in both cases (it is running 32-bit).
UPDATE: Per recommendation, I tried to run some prerelease builds to the same resulting, ending up with these binaries:
./Nancy.1.3-Pre1524/lib/net40/Nancy.dll
./Nancy.Authentication.Forms.1.3-Pre1524/lib/net40/Nancy.Authentication.Forms.dll
./Nancy.FlashMessages.1.0.4.0/lib/net45/Nancy.FlashMessages.dll
./Nancy.FlashMessages.Razor.1.0.4.0/lib/net45/Nancy.FlashMessages.Razor.dll
./Nancy.Hosting.Self.1.3-Pre1524/lib/net40/Nancy.Hosting.Self.dll
./Nancy.SimpleAuthentication.0.3.14/lib/net40/Nancy.SimpleAuthentication.dll
./Nancy.Viewengines.Razor.1.3-Pre1524/BuildProviders/Nancy.ViewEngines.Razor.BuildProviders.dll
./Nancy.Viewengines.Razor.1.3-Pre1524/lib/net40/Nancy.ViewEngines.Razor.dll
UPDATE: Running the ReflectionHelpers.cs code in isolation shows that the only DLL failing to load is MonoDevelop.NUnit. The NUnit dll is unneeded for this part anyhow.
I suppose I should contemplate https://github.com/SimpleAuthentication/SimpleAuthentication/issues/144
I fixed this with GetLoadableTypes from this post from #haacked http://haacked.com/archive/2012/07/23/get-all-types-in-an-assembly.aspx/
And here it's the PR (https://github.com/SimpleAuthentication/SimpleAuthentication/pull/171)
I didn't had the problem with Nunit I had the problem with Microsoft.Owin.Security.DataProtection.DpapiDataProtector that it's not implemented in Mono....