https://tenders.procurement.gov.ge/public/?go=190216&lang=ge
-
Run iis.config.bat using Run As Administrator
-
Add MSBuild in External Tools of Visual Studio,
-
Open Visual Studio,
-
Open Tools->External Tools
-
Click Add button
-
Enter in Titile - MSBuild
-
Enter in Command - C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe
-
Enter in Arguments - $(ItemPath)
-
Check Use Output window checkbox
-
Click OK button
-
In Solution Explorer select each CITI.EVO.CommonData.MSBuild.xml file after click on Tools->MSBuild
-
Do same as step 3 for each *.MSBuild.xml file
Here are the guidelines we would like you to follow:
Before you submit an issue, search the archive, maybe your question was already answered.
If your issue appears to be a bug, and hasn't been reported, open a new issue. Help us to maximize the effort we can spend fixing issues and adding new features by not reporting duplicate issues. Providing the following information will increase the chances of your issue being dealt with quickly:
- Overview of the Issue - if an error is being thrown a non-minified stack trace helps
- Motivation for or Use Case - explain what are you trying to do and why the current behavior is a bug for you
- Screenshots - Due to the visual nature of Angular Material, screenshots can help the team triage issues far more quickly than a text descrption.
- Related Issues - has a similar issue been reported before?
- Suggest a Fix - if you can't fix the bug yourself, perhaps you can point to what might be causing the problem (line of code or commit)
We have very precise rules over how our git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history. But also, we use the git commit messages to generate the change log.
Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject:
<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
The header is mandatory and the scope of the header is optional.
Any line of the commit message cannot be longer 100 characters! This allows the message to be easier to read on GitHub as well as in various git tools.
If the commit reverts a previous commit, it should begin with revert: , followed by the header of
the reverted commit. In the body it should say: This reverts commit <hash>., where the hash is
the SHA of the commit being reverted.
Must be one of the following:
- feat: A new feature
- fix: A bug fix
- docs: Documentation only changes
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- refactor: A code change that neither fixes a bug nor adds a feature
- perf: A code change that improves performance
- test: Adding missing tests or correcting existing tests
- build: Changes that affect the build system, CI configuration or external dependencies (example scopes: gulp, broccoli, npm)
- chore: Other changes that don't modify
srcortestfiles
The scope could be anything specifying place of the commit change. For example
tenders, settings, etc.
The subject contains succinct description of the change:
- use the imperative, present tense: "change" not "changed" nor "changes"
- don't capitalize first letter
- no dot (.) at the end
Just as in the subject, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change and contrast this with previous behavior.
The footer should contain any information about Breaking Changes and is also the place to reference GitHub issues that this commit Closes.
Breaking Changes should start with the word BREAKING CHANGE: with a space or two newlines.
The rest of the commit message is then used for this.