Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options user 70

For questions relating to ASP.NET MVC implementations. The ASP.NET MVC is a web application framework developed by Microsoft, which implements the model–view–controller pattern.

7
votes
properties with rendered Sitecore fields - the rest is really just basic MVC stuff. Don't try to over think the MVC stuff and let Sitecore get in the way of doing it simply. And don't do any of the above - use an ORM! …
answered Oct 5 '16 by Richard Seal
4
votes
As Mark mentioned, this post provides you with one answer, using extension methods. I believe what you want is simpler tho. The @Html.Sitecore().Field(....) method will return you a fully rendered <i …
answered Jun 7 '17 by Richard Seal
12
votes
Its because you are not using the Sitecore field render to render the field content. This code: var mainContent = Sitecore.Context.Item.Fields["Main Content"].Value; just outputs the raw value of t …
answered Jun 27 '17 by Richard Seal
6
votes
The problem here is that a controller rendering in the Sitecore world is not the same as a Controller action result in standard MVC. So you can't pass data through in the same way without custom …
answered Nov 11 '16 by Richard Seal
4
votes
Its not 3rd party - but you really should look into the Sitecore Experience Accelerator - while it doesn't have "controls" in the way you are thinking, it comes with a number of components/renderings …
answered Jul 10 '18 by Richard Seal
3
votes
The code looks like it should work. I would make the following changes to just make things a bit more robust: Add a [HttpGet] attribute to the Login action result. It could be that over https the ro …
answered Oct 18 '16 by Richard Seal
1
vote
Update So as a direct answer to your question - a PowerShell script can help with this as you have found. But this is not a good way of controlling environment config transforms. Doing it this way re …
answered Aug 6 '17 by Richard Seal
11
votes
Conditional renderings work fine with MVC. For version 8, you must have Analytics.Enabled set to true so you can get to the personalization section of the presentation. "Global" conditional … renderings do not work with MVC, so you need to stick to personalization of the rendering on the items presentation rather than a global rendering rule. Here is how you set a Personalization rule. Edit the …
answered Oct 6 '16 by Richard Seal
4
votes
The simplest solution here seems to be to update your custom controller A.B.Controllers.AuthenticationController to have a unique name so that it doesn't conflict with the Sitecore one. The risk of t …
answered Sep 28 '16 by Richard Seal
8
votes
It sounds like you have added the component to a placeholder key called section - with dynamic placeholders there will be an extra bit of data appended to that. Depending on the version of dynamic pla …
answered Dec 20 '16 by Richard Seal
1
vote
You could add your language as a parameter to the route. Something like this: routes.MapRoute("FormsApiWithLanguage", "{languageCode}/api/sitecore/Forms/SubmitForm", new { controller = "Forms …
answered Feb 9 '17 by Richard Seal
4
votes
To explain why you are getting that, @Html.Sitecore().Field requires a field name and the item to work with. Right now you are passing it a property on your model which is a string. To solve that you …
answered Jan 23 by Richard Seal
7
votes
I've done this before using a wildcard item for the parameter and a custom resolver processor that runs just after the ItemResolver - The ItemResolver should resolve to /sitecore/content/mysite/produc …
answered Oct 7 '16 by Richard Seal
8
votes
Yes - you are using the Raw Value when you do @Html.Raw(Model.SampleItem.Text.Raw) - this bypasses the field renderer and so will not be editable in the Experience Editor. Instead of .Raw use .Render …
answered Oct 6 '16 by Richard Seal
9
votes
So for Sitecore - a global error handler in the global.asax will not work properly. The better way to do it is to override the code that calls each rendering and handle the errors there. ExecuteRende …
answered Mar 7 '17 by Richard Seal

15 30 50 per page