I have an ASP.NET MVC 2 Beta app and have set <MvcBuildViews>true</MvcBuildViews>
in the property group at the top of my csproj file. But my views are not being compiled. A closer look at the .csproj file shows a squiggly under the MvcBuildViews tag and when I hover over it, it says
The element 'PropertyGroup'
in namespace
'http://schemas.microsoft.com/developer/msbuild/2003'
has invalid child element
'MvcBuildViews' in namespace
'http://schemas.microsoft.com/developer/msbuild/2003'.
List of possible elements expected:
'Property' in namespace
'http://schemas.microsoft.com/developer/msbuild/2003'.
What am I doing wrong?
Many elements you define in the .config are not part of that schema, but still operate. It's the same way for MSBuild scripts.
That's a custom property we include in the project files to compile views. It shouldn't cause any problems, since you can define your own properties (see http://msdn.microsoft.com/en-us/library/t4w159bs.aspx) in your project file.
For further detail, please refer to:
http://forums.asp.net/t/1506782.aspx?Error+invalid+child+element+MvcBuildViews+in+namespace
btw, this issue existed in 2009, but now is 2015, it still exists.
Related
I'm kinda new to typo, so maybe I am just missing something.
I'm trying to add a third content field to Typo3 4.5.
What I've done so far.
Edit my template and added a new block
Added the block via TemplatVoila > Update Mapping > Modify DS / TO with Element Preset "Page-Content Elements [Pos.: 0]
Mapped it to the new block in the template
But I am missing something as the new field isn't showing up in the Page edit screen.
EDIT: I've found the Block in the "Edit page properties" but how to show it on standard edit screen?
Any added content area will appear automatically in your TV-View-module. So if you dont see it in there, then
you may have duplicate fields names
wrong column positions
or the existing template is using a »beLayout«-section, which shows only the first two content areas (see example in reference http://docs.typo3.org/typo3cms/extensions/templavoila/ExtTemplavoila/StaticDataStructures/ExampleForBelayout/Index.html)
The TemplaVoila template is split into TS (TemplaVoilà Template Object) and DS (TemplaVoilà Data Structure) records, may you paste the content of the field „Data Structure XML“ of the DS record here? In there are all necessary information.
The two template files should be located in your general storage folder, your TypoScript root file should be there as well.
Since updating from Flux 6.0.2 to the newest Flux TER-Release (7.0.0) I have the problem that all my defined flux:field.select items are switched. I have them defined as an array like this items="{0: {0: 'value shown as a CSS class in the frontend',1: 'value shown in BE'},}". But now I get the BE value in the frontend template.
Also all my content elements from my provider extension are shown twice (without a title) in the backend and the fields defined in the 'Configuration' section of my content element are shown twice.
There's also a RTE field shown at the bottom of my content element that has not been there before.
BE Output: view
Code on Pastebin: http://pastebin.com/CNcphn2k
Any help deeply appreciated.
EDIT:
I just set up a fresh instance of TYPO3 6.1.9 (blank package) and installed my extension with the above mentioned content elements. Dependencies were resolved automatically as it should (newest versions). Via the content wizard I tried to create a new element and I get the same result as in my existing install I first noticed this bug in.
EDIT2:
I was able to narrow it down to the flux:form.container tag. This duplicates the output in the BE. The select values are still switched though.
It is possible that you missed this official announcement:
http://fluidtypo3.org/blog/news/new-colpos-value.html
Failure to run the update script before letting TYPO3 change the type of the colPos value will result in the symptoms you describe. There is, unfortunately, no way to restore this (since your SQL will have cropped off all negative values and made them zero without any backup).
Restore from a backup and run the script and you should be fine.
In my wicket application i have 3-4 different packages say pack1,pack2 and so on .
In pack1 i have different html and java classes. I am validating the null check by setRequired(true) and getting the message from properties file.I am naming my properties file as Send.properties ... as i have Send.html and Send.java in pack1.In properties file i am mentioning like this
formname.field.Required=The ${label} is missing
I want to validate all the html fields which are present in different html pages of the same package (pack1)in one properties file say pack1.properties .So my question here is will one singe properties will be sufficient for one package where in all the validation will be taken care.
Yes, wicket first looks for the property in the properties file associated to the page, and then in the properties asociated to the package (and after that in parents packages...).
But, as long as I know the package properties file is called package.properties (independently of the package name).
How would you see a specific file version in the ClearCase ?
How to set the right config spec for that specific file?
You can specify a specific selection rule for a specific file, but that won't help you actually accessing it.
For instance:
element /path/to/my/File /main/4
would select the version 4 of branch main only for /path/to/my/File.
But considering that the parent directories 'path', 'to', and 'my' have they own version (which isn't likely to be '4'), they won't be selected at all by that single rule.
(Don't forget that directories are versioned when their content changes: version 4 would mean their content have changed 4 times, in other words, that files or subdirectories have been added or removed 4 times)
To be sure to select the right version for a file, while being able to access it, you need 2 rules in the right order (as explained in "How to create a branch"):
element /path/to/my/File /main/4
element * /main/LATEST
That way, you would see the right version in your (snapshot or dynamic) ClearCase view for that file.
But that wouldn't allow to checkout it (no -mkbranch directive there).
If i make a label in TFS, and later make a new label with the same name... then the old label is replaced by the new one.
How do I prevent TFS from overwriting a label?
The following MSDN article covers using the Scope of a label to try and minimize the occurrences of these mishaps:
Using the /Child Option to Avoid Labeling Mishaps
If you issue a label command together with a pre-existing label name and an itemspec that includes files that are already marked by the same label, the value of the /child option determines whether the marked files are updated with new revision information. That is, the files are labeled by the same name, but have different scope.
Thanks, that led me on the right track.
It seems that the label overwrite is a "feature" and not a bug. It's working as designed
sixletter's link above explains it, and below are two more with info about it.
http://msdn.microsoft.com/en-us/library/ms181439(VS.80).aspx
http://msdn.microsoft.com/en-us/library/ms181440(VS.80).aspx
Apparently TFS labels are not a snaphot of a point in time like in other VCS's , though i do not fully understand the explanation.