Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / microsoft/vcrt-forwarders issues and pull requests
#48 - Missing msvcp140_codecvt_ids_app.dll
Issue -
State: open - Opened by amyw-msft 10 months ago
#47 - Add Checks to prevent inclusion in WinAppSDK Projects
Issue -
State: open - Opened by softworkz about 1 year ago
#46 - Update baseline
Pull Request -
State: closed - Opened by manodasanW about 1 year ago
#45 - Add pipeline and adopt to .NET breaking change
Pull Request -
State: closed - Opened by manodasanW about 1 year ago
#44 - Adding Microsoft SECURITY.MD
Pull Request -
State: closed - Opened by microsoft-github-policy-service[bot] over 1 year ago
#43 - Fixing issue with Configuration / Platform being empty
Pull Request -
State: closed - Opened by manodasanW almost 2 years ago
#42 - Broadly overhaul forwarder generation and update to 14.34.31931
Pull Request -
State: closed - Opened by DHowett almost 2 years ago
- 3 comments
#41 - All libraries in this repo should have VERSIONINFO resources
Issue -
State: closed - Opened by DHowett almost 2 years ago
#40 - Fix for #37
Pull Request -
State: closed - Opened by ocalvo almost 3 years ago
- 1 comment
#39 - Will VCRT forwarders always point to DLLs included in working directory for Unpackaged Win32 applications?
Issue -
State: open - Opened by taenri almost 3 years ago
#38 - Build fails on Azure pipeline when VCRTForwarders are added as nuget and there is anothe project reference.
Issue -
State: open - Opened by MonicaJa about 3 years ago
#37 - Build break when compiling WAP project
Issue -
State: closed - Opened by ocalvo over 3 years ago
- 1 comment
#36 - Impossible to load VCRT Forwarders if strict Control Flow Guard is enabled
Issue -
State: open - Opened by sylveon over 3 years ago
- 1 comment
#35 - No PDBs included for the DLLs
Issue -
State: closed - Opened by amp64 over 3 years ago
#34 - The recursive MSBuild task UseDebugCRT forces incorrect solution build
Issue -
State: open - Opened by DHowett almost 4 years ago
- 1 comment
Labels: bug
#33 - ARM32
Issue -
State: closed - Opened by kennykerr almost 4 years ago
- 1 comment
#32 - Adds support for building VCRT Forwarders as a UPM package
Pull Request -
State: closed - Opened by david-c-kline about 4 years ago
- 2 comments
#31 - .NET RID not supported
Issue -
State: open - Opened by nxtn over 4 years ago
- 1 comment
Labels: bug
#30 - "debug"/"release" folder not honored by .NET CLI
Issue -
State: open - Opened by nxtn over 4 years ago
#29 - Handle error when we can't determine configuration of project references
Pull Request -
State: closed - Opened by manodasanW over 4 years ago
#28 - v1.0.6 regression: cannot build a solution project in isolation, ProjectReferenceWithConfiguration undefined
Issue -
State: closed - Opened by Scottj1s over 4 years ago
Labels: bug
#27 - Simplify the evaluation of VCRTForwarders-IncludeDebugCRT.
Pull Request -
State: closed - Opened by jlaanstra over 4 years ago
- 2 comments
#26 - Update InitVCRTForwarders.cs
Pull Request -
State: closed - Opened by StephenHodgson over 4 years ago
- 1 comment
#25 - VCRTForwarder binaries are not accessible in Unity Standalone projects
Issue -
State: open - Opened by dfields-msft over 4 years ago
Labels: bug
#24 - AddDllDirectory fails when dlls/c# files are placed in a unity package compared to in the project Assets folder
Issue -
State: open - Opened by chrisfromwork over 4 years ago
- 2 comments
Labels: bug
#23 - VCRT Forwarders Initializer breaks iOS/Mac builds
Issue -
State: open - Opened by chrisfromwork over 4 years ago
- 3 comments
Labels: bug
#22 - Need support for netcoreapp5.0 TFM
Issue -
State: open - Opened by Scottj1s over 4 years ago
- 1 comment
Labels: enhancement
#21 - Update readme with details of custom configurations.
Pull Request -
State: closed - Opened by manodasanW over 4 years ago
#20 - Adding support for custom configurations
Pull Request -
State: closed - Opened by manodasanW over 4 years ago
#19 - Using a custom Configuration doesn't work with VCRT Forwarders
Issue -
State: closed - Opened by Austin-Lamb over 4 years ago
- 1 comment
#18 - Binaries are set to Debug/Release configurations instead of _DEBUG macro
Issue -
State: closed - Opened by AndreyChistyakov over 4 years ago
#17 - Using the publish option in Visual Studio does not copy the dlls to the target directory
Issue -
State: closed - Opened by lhak almost 5 years ago
Labels: bug
#16 - Add support for MSBuildForUnity
Pull Request -
State: closed - Opened by majaeger almost 5 years ago
- 1 comment
#15 - Increment patch version and add release notes
Pull Request -
State: closed - Opened by dfields-msft almost 5 years ago
#14 - Add asmdef file for Unity editor scripts
Pull Request -
State: closed - Opened by majaeger almost 5 years ago
- 1 comment
#13 - Do not include VCRTForwarder libs if AppContainerApplication is set t…
Pull Request -
State: closed - Opened by majaeger about 5 years ago
- 1 comment
#12 - Forwarder binaries are included in the app package for CppWinrt apps if the forwarders nuget package is installed
Issue -
State: open - Opened by majaeger about 5 years ago
- 2 comments
Labels: bug
#11 - Consider linking with /NOENTRY option
Issue -
State: closed - Opened by rsola about 5 years ago
- 1 comment
Labels: enhancement, P2
#10 - Add missing Unity .meta files
Pull Request -
State: closed - Opened by dfields-msft about 5 years ago
#9 - Added support for NuGet for Unity
Pull Request -
State: closed - Opened by dfields-msft about 5 years ago
#8 - PublishSingleFile error on .NET Core 3.0 Preview 8 "Invalid input specification: Found multiple entries with the same BundleRelativePath"
Issue -
State: open - Opened by sudoudaisuke over 5 years ago
- 11 comments
Labels: bug, P1
#7 - Binaries are not automatically copied to the output directory for managed projects
Issue -
State: open - Opened by dfields-msft over 5 years ago
- 5 comments
Labels: enhancement, P1
#6 - Updating forwarders
Pull Request -
State: closed - Opened by manodasanW over 5 years ago
#5 - Adding script to generate forwarders
Pull Request -
State: closed - Opened by manodasanW over 5 years ago
#4 - Make project forkable/buildable
Issue -
State: closed - Opened by Scottj1s over 5 years ago
#3 - Debug targets have both binaries debug and release
Issue -
State: closed - Opened by Sudhaushu over 5 years ago
- 1 comment
#2 - ARM and ARM64 libraries missing
Issue -
State: closed - Opened by Sudhaushu over 5 years ago
- 5 comments
#1 - What is the point of this repository?
Issue -
State: closed - Opened by wjk over 5 years ago
- 2 comments