publisher-policy

How to reference shared assemblies that are still under development (.NET)

由 冷暖自知 提交于 2019-12-21 06:24:08
问题 I am responsible for developing and maintaining a set of common, framework assemblies that are used to build our product applications. These assemblies are relatively new and in a state of flux as new features are implemented, etc. As a result, it is not unusual for them to be rebuilt and redistributed somewhat frequently. I would expect this to decrease as the assemblies are stabalized, but it is what it is today. Right now, the assemblies are placed into a Common folder where the

.NET Publisher Policy Target Framework

由 这一生的挚爱 提交于 2019-12-13 07:35:03
问题 SUMMARY How do I create a publisher policy assembly that targets the same framework version as the redirected assembly? TL;DR I have an Assembly.dll with version 1.x.y.0 and I also have a publisher policy for it named policy.1.0.Assembly.dll which redirects versions 1.0.0.0-1.x.y.0 to 1.x.y.0 . The Assembly.dll targets .NET Framework 3.5. Am I right in thinking that the policy.1.0.Assembly.dll should also target .NET Framework 3.5 for things to work correctly on all frameworks 3.5+? If yes,

How to reference shared assemblies that are still under development (.NET)

由 隐身守侯 提交于 2019-12-03 22:17:11
I am responsible for developing and maintaining a set of common, framework assemblies that are used to build our product applications. These assemblies are relatively new and in a state of flux as new features are implemented, etc. As a result, it is not unusual for them to be rebuilt and redistributed somewhat frequently. I would expect this to decrease as the assemblies are stabalized, but it is what it is today. Right now, the assemblies are placed into a Common folder where the development projects can reference the same assemblies. Applying updates is as simple as replacing the files and
订阅 publisher-policy