You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are in the middle of transition from old style to SDK style for our projects. We noticed that for exe types, msbuild will generate additional file apart of exe and exe.config. Because of that our integration pipelines will fail as they will not expect such files to be produced. File end with "*.withSupportedRuntime.config". There doesn't seems to be much info what this file do in addition to exe.config. Do we really need those files to be deployed. And most importantly. Can we stop msbuild generating them ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are in the middle of transition from old style to SDK style for our projects. We noticed that for exe types, msbuild will generate additional file apart of exe and exe.config. Because of that our integration pipelines will fail as they will not expect such files to be produced. File end with "*.withSupportedRuntime.config". There doesn't seems to be much info what this file do in addition to exe.config. Do we really need those files to be deployed. And most importantly. Can we stop msbuild generating them ?
Beta Was this translation helpful? Give feedback.
All reactions