The below script can be used to cleanup outdated artifacts in Artifactory. It uses REST API to scan and delete items by age. Make sure you use Powershell 5.
You can get this message if you are using tfs proxy. The source control proxy 'xxxxxxxxx' is not responding, so the request will be sent to the main server. Please verify your settings. Additional information: TF30063: You are not authorized to access Microsoft-IIS/7.5. ---- Summary: 0 conflicts, 1 warnings, 0 errors ---- Solution: Go to Control Panel\Credential Manager and add your tfs credentials for proxy server.
Fast up-to-date check was created in an attempt to mitigate performance issues with incremental builds in MSBUILD. Indeed if you have many projects it would take considerable amount of time to evaluate each of them and check timestamps on all input and output files. Instead Microsoft decided to implement a simplified version of these checks that would run faster without involving MSBUILD engine. As a result this "feature" only works with "native" targets and if you have any kind of customization where external inputs or outputs are used then you'll have "misfires" sometimes. Below is some information I was able to figure out that can help you mitigate those issues. It's based on my own investigation therefore it may be not accurate enough. At least this is the most complete description that you'll find on the web. It will help you a lot in troubleshooting if you enable up-to-date check logging. Go to HKEY_CURRENT_USER\Software\Microsoft\Visua...
IISExpress which comes with Visual Studio only supports absolute paths to webroot in applicationhost.config. Visual Studio updates this file with actual path when you load web project. Basically you cannot use IISExpress if your web-site is hosted in a different folder other than original webroot. However in solutions with multiple web projects where they are linked to a single common webroot folder it may become a problem. In order to override Visual Studio behavior I wrote MSBUILD script which updates applicationhost.config with necessary path. You'll also need to include applicationhost.config into your web-project as a link to make sure Visual Studio doesn't skip build when file changed.
Comments
Post a Comment