Where is a complete reference of ALL MsBuild properties ?? Like this
$(OutDir)
$(OutputPath)
$(TargetName)
$(TargetExt)
...
The MSDN reference is here
Common MSBuild Project Properties
MSBuild Reserved Properties
It sounds like there can be more project-type-specific properties; which project types are you dealing with?
Related
I have a question related to Kademi platform. In normal page templating, I can use #docs for exploring properties and methods of an object but in EDM template, I can not. Do you know how to do that?
You can use #docs in theme/emailBase.html
Variables specific to automation are copied into the templating model for the base template, so can be referenced from $page.model.xxx, where xxx is the same variable name as in the automation template
For example, if you're writing an automation template for an event, and you're not sure what the event is and what properties it has, use this;
#docs($page.model.event)
I have a workflow containing 3 activities. The external variable that is used throughout the workflow is of type Dictionary which contains only two fields: EmailAddress and PhoneNumber(all strings). This is the screenshot of the workflow
So the scenario is that the activity GetParticipant has an outargument of type Dictionary which I am assigning to an external variable called pax. Using the if condition I am checking if the EmailAddress is provided or not.
My problem is that I am getting an error at the if condition:
Reference required to assembly 'Microsoft.WindowsAzure.Storage, Version=4.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' containing the base class 'Microsoft.WindowsAzure.Storage.Table.TableEntity'. Add one to your project.
The mentioned reference is already added to the project and the workflow also imports it. But the error remains. However giving only True as the condition works. What am I doing wrong?
Its seems some reference issue as i can see one bubble near if condition.
Check for dependency of mentioned Dll, can use nugget manager.
You can do below steps.
Delete reference of dll and import.
Clean solution and add reference and set property copy local true and import the namespace in workflow.
Rebuild the solution.
I am new to NAnt script. So I want to know the usage of properties and attribute in NAnt .Can anyone tell me what is the Purpose of Property and attribute in NAnt scripting
The answer is in a comment: Properties are like variables you can use throughout your script. Attributes are identical to how they're used in XML - they provide configuration details to tasks.
I'm trying to use this code in Powershell:
Add-Type -AssemblyName "System.Collections.Generic"
However I get this error:
Add-Type : Cannot add type. One or more required assemblies are missing.
I've looked in C:\windows\assembly\GAC_MSIL and can see that there is no folder named System.Collections.Generic.
Do I need to download this library, if so where?
There is no System.Collections.Generic assembly. That is a namespace. A large portion of the types in that namespace are in the core library assembly, mscorlib.dll which is already available in Powershell since Powershell is .Net.
Go to MSDN for the namespace, find the type you are trying to use, and you can see the assembly it is in, and remember that there is not necessarily a one to one relationship between assemblies and namespaces.
Using generic types is a bit involved in Powershell and can depend on using reflection, or formatting complex type names.
See this stackoverflow question for some more details.
Never mind,
not sure why that doesn't work, but turns out I don't need it anyway.
I had this code which for some reason wasn't working intially because it couldn't find [Collections.Generic.List[String]], but now it seems to work:
[string[]] $csvUserInfo = #([IO.File]::ReadAllLines($script:EmailListCsvFile))
[Collections.Generic.List[String]]$x = $csvUserInfo
I would answer by another question, Why do you need this assembly ?
Can you try to replace your code by :
$x = [IO.File]::ReadAllLines($script:EmailListCsvFile)
In PowerShell it should work.
I am looking for information to which PRIMS/MVVM ddls I have to reference to in my project to have available Prism/MVVM functionality for handling Commands. I plan to use only this part of the frameworks.
Regards,
Wojtek
If you only want commanding support I would suggest to completely avoid Prism and that way you will reduce the size of your .xap file.
I would suggest you to look at the code (either in Reflector or open Prism's source) and copy to your project all the files in "Microsoft.Practices.Composite.Presentation.Commands" namespace in the "Microsoft.Practices.Composite.Presentation" assembly. You can ignore CompositeCommand.
If you prefer to reference the assembly, go with "Microsoft.Practices.Composite.Presentation". If you only use commands you won't need other assemblies. The compiler will tell you in case start using other classes from that assembly that depend on another one. The other two dependencies for this assembly (for classes other than commands) are "Microsoft.Practices.Composite" and "Microsot.Practices.ServiceLocation".