MVC 4 Display Correct Date Format in Edit Mode

This works:

@Html.TextBox("DateOrdered", string.Format("{0:d}", Model.DateOrdered))

MVC 4, EF5 Code First - Forcing a Decimal to x Number of Places

Stick this in your DB Context if you need to have EF recongise more than two decimal places.

  protected override void OnModelCreating(DbModelBuilder modelBuilder)  
     {  
       // We have a Decimal Field in Our SQL Table decimal(18, 4)  
       // By default only the first two digits after the decimal will be recognised if this property is set to type decimal  
       // we need to override this behaviour and here's how  
       modelBuilder.Entity<MyObjec t>().Property(f => f.totalWeightMg).HasPrecision(18,4);       
       base.OnModelCreating(modelBuilder);  
     }  

Return Yes, No from Boolean instead of True, False

I recently needed to output Boolean values into an iTextSharp PDF document having them represented as Yes or No rather than True or False

Cue MSDN. This article Boolean Structure explains how to do this.

Here's a quick example:

bool JobDone = true;
string strJobDone = JobDone ? "Yes" : "No"; // Returns "Yes"

MVC4 Entity Framework and Decimal Precision

This just caught me out today so hopefully it will help someone else.

Stack Overflow answer here http://stackoverflow.com/questions/3504660/decimal-precision-and-scale-in-ef-code-first

If you have a database field with the spec decimal(18,5) the Entity Framework will still round the number to 2 decimal places by default, so if you enter a number e.g. 15.42700 it will be saved to your database as 15.42000, not very helpful eh. Anyway to fix it you need to override OnModelCreating in your DBContext Class

public class EFDbContext : DbContext { protected override void OnModelCreating(System.Data.Entity.DbModelBuilder modelBuilder) { modelBuilder.Entity().Property(object => object.property).HasPrecision(12, 10); base.OnModelCreating(modelBuilder); } }

Getting to Grips with Sharepoint Foundation 2013 REST API

I'm finding myself constantly struggling against the OOB (Out Of Box) features of Sharepoint Foundation 2013 and often need to find ways to interact with Lists in ways that are just not available. Enter the REST API. If, like me, you need to get to grips with using the Sharepoint REST API then I recommend the article SharePoint: Adventures with the REST API Part 1 which is by far the best guide I have found on them t'interwebs.

Autocomplete Lookup Field in Sharepoint Foundation 2013

Recently I've been working on a project where there are several related Lists, in this particular instance a list of Appointments and Patients. So the Appointments List has a Lookup field Patient. By default this gives you a select or drop down list, not ideal if you end up with several items on the list.

I eventually stumbled across SharePoint 2013 Autocomplete Lookup Field. Pretty straightforward to install provided you have server access and works like a charm. Highly recommeded.

Adding a simple Chat Facility to a Sharepoint Foundation 2013 Site

I've recently been working on a Sharepoint Project where the client requires their receptionist to be able to send them messages without flooding their email. So they asked for some kind of chat or instant messaging facility. I stumbled across Simple Chat a basic, lightweight JQuery based script which does the job very well.

Implementing the script is really easy. Here's the short version:

• Create a Document Library to store your JavaScript files.
• Create a Custom List to display your messages
• Add a Script Editor Web Part to where you want to keep your Chat facility. Edit Snippet, add JQuery code etc.

Job done.

Restore Content Types in Sharepoint Foundation 2013

If you find yourself in the situation where you've messed up with the Content Types in a Sharepoint Site Collection then this will help restore everything back to the default settings:

Open - Start - All Programs - Microsoft Sharepoint Products - Sharepoint Management Shell and run this:

stsadm -o deactivatefeature -name Fields -url http://sitecoll -force
stsadm -o activatefeature -name Fields -url http://sitecoll -force

Source: http://sharepoint.stackexchange.com/questions/8517/site-content-types-screwed-up-how-to-restore-to-default/26225#26225?newreg=0c4f241b46ab466ea0d265069efdca5f

SharePoint Foundation 2013 Forms Based Authentication (FBA)

Scenario

You need to have individual Forms Based Authentication (FBA) on several different Sharepoint Foundation 2013 Site Collections.

Solution

1. Run c:\windows\Microsoft.NET\Framework64\v4.0.30319\ aspnet_regsql.exe to set up Membership Database
2. Give Identity Running Sharepoint "db_owner" priveleges in MSSMS for the aspnetdb database.
3. Create a Dummy Website in IIS "MembershipConfig"
4. Install FBA for SharePoint 2013 - This allows management of users inside sharepoint
5. Edit machine.Config File
6. Configure Forms Auth in Sharepoint for Site Collection

Caveats

• Use SQL Authentication for ALL Connection Strings and DB User Accounts.

Resources

Here's a list of the resources I found which helped get the job done:

• Configuring Forms Based Authentication in SharePoint 2013 – Part 1 – Creating the Membership Database - Chris Coulson's Developer Notes
• Configuring SharePoint 2013 Forms-Based Authentication with SQLMemberShipProvider - Partner Technical Services Blog
• SharePoint 2013 Forms Based Authentication (FBA)- Random Technical Thoughts
• Configure Forms Based Authentication for SharePoint 2013 -
• Configuring claims and forms based authentication for use with a SQL provider in SharePoint 2010
• Easy-Bake Forms Based Authentication - SharePoint Voodoo
• Forms Based Authentication FBA In SharePoint 2010 Claims
• SharePoint 2013 FBA Pack

Searching Model Data based on string and integer field types

Scenario

You need to add a search function based on model data based on searching both string and int datatypes. If you try the obvious method in your LINQ query as just converting your int field ToString you end up with an error similar to this:

ToString is not supported in linq to entities

Or even this bad boy:

LINQ to Entities does not recognize the method 'System.String ToString()' method, and this method cannot be translated into a store expression.

After trawling around the forums for a good hour or so I found the following solution. Hope it helps someone else too.

 public ActionResult Search(string search = null)  
     {  
       int intSearch;  
       if (!Int32.TryParse(search, out intSearch))  
       {  
       }  
       IEnumerable<Car> cars = context.Cars.Where(  
            c => search == null  
              || c.IntegerField == intSearch  
              || c.Manufacturer.Contains(search)  
              || c.Model.Contains(search)             
             );  
       cars = cars.OrderBy(c => c.Id).ToList();  
       ViewBag.Search = search;  
       return View(cars);  
     }