Sample Professional Growth Plan Goals Performance Assessment: Design and implement two high‐quality performance assessments per academic year that require transfer and application of new learning. Continue the development of performance tasks by developing new tasks and aligning the rubrics to tasks.
There are three potential causes of off-task behavior by students. The first is defiance. Students can be off task because they simply don't want to do what you've asked and don't care if you feel otherwise. The second is incompetence. I use that word in a nonjudgmental sense merely to refer to those times when students don't yet have the skill to do a task reliably. Finally, there's opportunism. Students see a gray area and lack of clarity about what's supposed to be happening, so they take advantage of it to act on the most convenient or enjoyable interpretation of the situation.
- 2.0 MANAGEMENT APPROACH. XYZ Company proposes a performance based service oriented solution that includes systems analysis, integration, and program management skills necessary to manage the development and operations of the AGENCIES's mission critical systems. To ensure we meet the program.
- But you only have so much time, and you can only get a finite number of things done in a day. Making a 1-3-5 list before you get started means the things you will get the most important tasks accomplished. Of course, this can be flexible. If you spend much of your day in meetings, for example, you might need to cut your number of items down.
- Have a positive attitude. Don't wrap yourself (and co-workers) in the story that you have too.
What to Do is a profoundly simple technique, involving giving directions in a format that clearly describes what you want in concrete terms—as opposed to giving instructions in vague and confusing terms, or telling students what not to do. In schools, we may issue a lot of vague, inefficient, and unclear commands, even without realizing it: 'Don't get distracted.' 'Stop that.' 'That behavior was inappropriate.' They force students to guess at what you want them to do. This gray area leaves the door open to inaccurate interpretations, making it harder for students to do as you've asked, both now and in the future.
You need to be able to distinguish incompetence from defiance by making commands specific enough that they can't be deliberately misinterpreted, and helpful enough that they explain away any gray areas. If I ask John to pay attention, sit up, or get on task, and he doesn't, it's crucial that I know whether he cannot or will not. If he cannot, the problem is incompetence. If he will not, the problem is defiance. How I respond depends entirely on what the root of the problem is.
If the issue is incompetence, I must teach John. If I punish him for not complying when he is unable to do so, the consequence will seem unjust and may erode my relationship with him. Consequences may appear random and disconnected from his actions. Learned helplessness—the process of giving up because you believe your own choices and actions are irrelevant—generally results from a perception that consequences are random. If the issue is defiance, my obligation is to provide a consequence. Unless I act clearly and decisively in the face of a challenge to my authority, John will establish a precedent of impunity. If I respond to defiance with teaching, I am just as bad off as I am if I respond to incompetence with punishment.
Confusing incompetence and defiance has damaging consequences, and this is why making the distinction reliably and consistently has such far-reaching ramifications for your classroom. By giving concrete, specific, observable, and sequential directions, you can make the distinction consistently and fairly—responding by teaching when you should teach and exerting your authority when you must.
What to Do not only canmake a big difference in your students' follow-through but also can improve your relationships with them. It socializes us as teachers to reflect on the quality of our directions before we proceed with other (and potentially more forceful) behavior management approaches.
-->Azure Pipelines | Azure DevOps Server 2020 | Azure DevOps Server 2019 | TFS 2018 | TFS 2017
Azure Pipelines
Use this task to build, test, package, or publish a dotnet application, or to run a custom dotnet command. For package commands, this task supports NuGet.org and authenticated feeds like Package Management and MyGet.
If your .NET Core or .NET Standard build depends on NuGet packages, make sure to add two copies of this step: one with the restore command and one with the build command.
Note
In Microsoft Team Foundation Server (TFS) 2018 and previous versions,build and release pipelines are called definitions,runs are called builds,service connections are called service endpoints,stages are called environments,and jobs are called phases.
Arguments
| Argument | Description |
|---|---|
commandCommand | The dotnet command to run. Select custom to add arguments or use a command not listed here.Options: build, push, pack, publish, restore, run, test, custom |
selectOrConfigFeeds to use | You can either choose to select a feed from Azure Artifacts and/or NuGet.org here, or commit a NuGet.config file to your source code repository and set its path using the nugetConfigPath argument.Options: select, configArgument aliases: feedsToUse |
versioningSchemeAutomatic package versioning | Cannot be used with include referenced projects. If you choose 'Use the date and time', this will generate a SemVer-compliant version formatted as X.Y.Z-ci-datetime where you choose X, Y, and Z.If you choose 'Use an environment variable', you must select an environment variable and ensure it contains the version number you want to use. If you choose 'Use the build number', this will use the build number to version your package. Note: Under Options set the build number format to be '$(BuildDefinitionName)_$(Year:yyyy).$(Month).$(DayOfMonth)$(Rev:.r)' |
argumentsArguments | Arguments to the selected command. For example, build configuration, output folder, runtime. The arguments depend on the command selected Note: This input only currently accepts arguments for build, publish, run, test, custom. If you would like to add arguments for a command not listed, use custom. |
projectsPath to project(s) | The path to the csproj file(s) to use. You can use wildcards (e.g. **/*.csproj for all .csproj files in all subfolders). |
noCacheDisable local cache | Prevents NuGet from using packages from local machine caches. |
restoreArgumentsRestore arguments | Write the additional arguments to be passed to the restore command. |
packagesDirectoryDestination directory | Specifies the folder in which packages are installed. If no folder is specified, packages are restored into the default NuGet package cache Argument aliases: restoreDirectory |
buildPropertiesAdditional build properties | Specifies a list of token = value pairs, separated by semicolons, where each occurrence of $token$ in the .nuspec file will be replaced with the given value. Values can be strings in quotation marks |
verbosityPackVerbosity | Specifies the amount of detail displayed in the output for the pack command. |
verbosityRestoreVerbosity | Specifies the amount of detail displayed in the output for the restore command. |
workingDirectoryWorking Directory | Current working directory where the script is run. Empty is the root of the repo (build) or artifacts (release), which is $(System.DefaultWorkingDirectory) |
searchPatternPushPath to NuGet package(s) to publish | The pattern to match or path to nupkg files to be uploaded. Multiple patterns can be separated by a semicolon, and you can make a pattern negative by prefixing it with !. Example:**/*.nupkg;!**/*.Tests.nupkg.Argument aliases: packagesToPush |
nuGetFeedTypeTarget feed location | Specifies whether the target feed is internal or external. Options: internal, external |
feedPublishTarget feed | Select a feed hosted in your organization. You must have Package Management installed and licensed to select a feed here Argument aliases: publishVstsFeed |
publishPackageMetadataPublish pipeline metadata | Associate this build/release pipeline's metadata (run ID, source code information) with the package |
externalEndpointNuGet server | The NuGet service connection that contains the external NuGet server's credentials. Argument aliases: publishFeedCredentials |
searchPatternPackPath to csproj or nuspec file(s) to pack | Pattern to search for csproj or nuspec files to pack. You can separate multiple patterns with a semicolon, and you can make a pattern negative by prefixing it with !. Example:**/*.csproj;!**/*.Tests.csprojArgument aliases: packagesToPack |
configurationToPackConfiguration to Package | When using a csproj file this specifies the configuration to package. Argument aliases: configuration |
outputDirPackage Folder | Folder where packages will be created. If empty, packages will be created alongside the csproj file. Argument aliases: packDirectory |
nobuildDo not build | Don't build the project before packing. Corresponds to the --no-build parameter of the `build` command. |
includesymbolsInclude Symbols | Additionally creates symbol NuGet packages. Corresponds to the --include-symbols command line parameter. |
includesourceInclude Source | Includes source code in the package. Corresponds to the --include-source command line parameter. |
publishWebProjectsPublish Web Projects | If `true`, the `projects` property value will be skipped and the task will try to find the web projects in the repository and run the publish command on them. Web projects are identified by presence of either a web.config file or wwwroot folder in the directory. Note that this argument defaults to `true` if not specified. |
zipAfterPublishZip Published Projects | If `true`, folder created by the publish command will be zipped and deleted. |
modifyOutputPathAdd project name to publish path | If `true`, folders created by the publish command will have project file name prefixed to their folder names when output path is specified explicitly in arguments. This is useful if you want to publish multiple projects to the same folder. |
publishTestResultsPublish test results | Enabling this option will generate a test results TRX file in $(Agent.TempDirectory) and results will be published to the server. This option appends --logger trx --results-directory $(Agent.TempDirectory) to the command line arguments.Code coverage can be collected by adding --collect 'Code coverage' to the command line arguments. This is currently only available on the Windows platform. |
testRunTitleTest run title | Provides a name for the test run |
customCustom command | The command to pass to dotnet.exe for execution. For a full list of available commands, see the dotnet CLI documentation |
feedRestoreUse packages from this Azure Artifacts/TFS feed | Include the selected feed in the generated NuGet.config. You must have Package Management installed and licensed to select a feed here. projectName/feedName for project-scoped feed. FeedName only for organization-scoped feed. Note that this is not supported for the test command. Argument aliases: vstsFeed |
includeNuGetOrgUse packages from NuGet.org | Include NuGet.org in the generated NuGet.config0000. |
nugetConfigPathPath to NuGet.config | The NuGet.config in your repository that specifies the feeds from which to restore packages. |
externalEndpointsCredentials for feeds outside this organization/collection | Credentials to use for external registries located in the selected NuGet.config. For feeds in this organization/collection, leave this blank; the build's credentials are used automatically Argument aliases: externalFeedCredentials |
versionEnvVarEnvironment variable | Enter the variable name without $, $env, or % |
requestedMajorVersionMajor | The 'X' in version X.Y.Z. Argument aliases: majorVersion |
requestedMinorVersionMinor | The 'Y' in version X.Y.Z. Argument aliases: minorVersion |
requestedPatchVersionPatch | The 'Z' in version X.Y.Z. Argument aliases: patchVersion |
| Control options |
Examples
Build
Build a project
Build Multiple Projects
Push
Push NuGet packages to internal feed
Push NuGet packages to external feed
Pack
Pack a NuGetPackage to a specific output directory
Plan Your Tasks 2 0 2nd
Pack a Symbol Package
Publish
Publish projects to specified folder
Restore
Test
Run tests in your repository
FAQ
Why is my build, publish, or test step failing to restore packages?
Most dotnet commands, including build, publish, and test include an implicit restore step. This will fail against authenticated feeds, even if you ran a successful dotnet restore in an earlier step, because the earlier step will have cleaned up the credentials it used.
To fix this issue, add the --no-restore flag to the Arguments textbox.
In addition, the test command does not recognize the feedRestore or vstsFeed arguments and feeds specified in this manner will not be included in the generated NuGet.config file when the implicit restore step runs. It is recommended that an explicit dotnet restore step be used to restore packages. The restore command respects the feedRestore and vstsFeed arguments.
Why should I check in a NuGet.config?
Checking a NuGet.config into source control ensures that a key piece of information needed to build your project-the location of its packages-is available to every developer that checks out your code.
However, for situations where a team of developers works on a large range of projects, it's also possible to add an Azure Artifacts feed to the global NuGet.config on each developer's machine. In these situations, using the 'Feeds I select here' option in the NuGet task replicates this configuration.
Troubleshooting
File structure for output files is different from previous builds
Azure DevOps hosted agents are configured with .NET Core 3.0, 2.1 and 2.2.CLI for .NET Core 3.0 has a different behavior while publishing projects using output folder argument. When publishing projects with the output folder argument (-o), the output folder is created in the root directory and not in the project file's directory. Hence while publishing more than one project, all the files are published to the same directory, which causes an issue.
To resolve this issue, use the Add project name to publish path parameter (modifyOutputPath in YAML) in the .NET Core CLI task. This creates a sub folder with project file's name, inside the output folder. Hence all your projects will be published under different subfolder's inside the main output folder.
Project using Entity Framework has stopped working on Hosted Agents
The latest .NET Core: 3.0 does not have Entity Framework(EF) built in. You will have to either install EF before beginning execution or add global.json to the project with required .NET Core SDK version. This will ensure that correct SDK is used to build EF project. If the required version is not present on the machine, add UseDotNetV2 task to your pipeline to install the required version.Learn more about EF with .NET Core 3.0
Open Source
Plan Your Tasks 2 0 2013
This task is open source on GitHub. Feedback and contributions are welcome.
