In a finder window press CMD + SHIFT + . to toggle show/hide hidden files.
With a single user on MacOS the login screen background should be a blurred version of the desktop background. However sometimes when picking a new desktop background the login background defaults to standard MacOS background. To resolve this do the following.
- Pick a different desktop background to the actual one you want to use.
- In the Finder, choose Go > Go To Folder.
- Paste the following and press return: /Library/Caches.
- Delete the file named com.apple.desktop.admin.png.
- In the Desktop & Screen Saver preference pane, select the desktop background you want.
- After a few seconds the com.apple.desktop.admin.png should be recreated using your new background image.
Visual Studio 2017 comes bundled with a version of Chrome which integrates with the VS debugging tools. It’s enabled by default and can be quite useful. However as it’s not the same version of Chrome you may have installed on your machine, it doesn’t give access to your bookmarks, browser extensions etc.
This feature can be disabled:
1. Go to Tools > Options.
2. Select Debugging then General.
Next time you run your web application Visual Studio will use whichever version of Chrome/IE you have installed.
If you are intending to use the same namespace across multiple views, just include it in the web.config of the Views folder. In the following example I wanted the MyProject.WebUI.Properties namespace to be available to all views. The removes the need to add the using statement for this namespace to every view. Please note, once you’ve added the namespace you’ll need to close and reopen any open view files for intellisence to recognize the namespace.
<system.web.webPages.razor> <host factoryType="System.Web.Mvc.MvcWebRazorHostFactory, System.Web.Mvc, Version=126.96.36.199, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /> <pages pageBaseType="System.Web.Mvc.WebViewPage"> <namespaces> <add namespace="System.Web.Mvc" /> <add namespace="System.Web.Mvc.Ajax" /> <add namespace="System.Web.Mvc.Html" /> <add namespace="System.Web.Routing" /> <add namespace="MyProject.WebUI.Properties" /> </namespaces> </pages> </system.web.webPages.razor>
By default Visual Studio will create a Navigation Control with an attached TableViewController. However if you need a different View Controller it’s quite simple to change it.
You can just delete the TableViewController, Drag and drop a new UIViewController into the StoryBoard, then (holding down Control) Click and drag a “connection” from your NavigationController to the new UIViewController you just added and select “root view”
This is easy when using Classic mode for deploying your virtual machine. Once deployment is complete the RDP port will default to 3389.
To change this:
- Select Virtual machines (Classic).
- Select the virtual machine you want to change the port for.
- Select Endpoints.
- Change the public port for both RDP TCP and RDP UDP endpoints to the desired number. DO NOT change the private port.
Sitecore revealed the latest version of their customer experience platform at the Los Vegas Symposium 2017, Sitecore 9. The following is brief overview of whats available.
Sitecore have changed the name from Customer Experience Platform to Experience Cloud.
xConnect is a new API which allows developers to integrate data collected by Sitecore with other third party sources. Reading data from the xDB has now been standardised via the xConnect service layer.
Cortex is a new machine learning engine purpose build for Sitecore. It helps discover new audiences and is able run multi-varient tests. Future development of Cortex will bring automated personalisation and is expect to make an appearance towards the latter part of 2018.
First quarter 2018 will bring Sitecore Commerce 9. This will bring a more mature and fully integrate e-commerce solution. Build in .Net Core the new solution will replace Commerce Server. The old store front will be replaced by SXA compomants.
Microsoft and Sitecore have improved the offerings available from the Azure Marketplace. Its now possible to pick your Sitecore version (all 8.2’s and 9) along with topology and size. While is a simple and quick way to spin up a Sitecore install your are limited to pre-made packages. For customer installs, its still advisable to use the Azure Resource Manager (ARM) templates instead.
Web Forms For Marketers (WFFM) has finally been replaced. Sitecore Forms has new look with full drag and drop support. It also includes multipage forms and conditional logic.
Sitecore finally offers federated authentication via OWIN. This provides integration with SAML, Facebook, OAuth, WS-Federation and ADD.
Sitecore is moving away from its proprietary UI framework (SPEAK) to a commodity based strategy, Angular First.
Sitecore Installation Framework (SIF)
Installing Sitecore 9 is different from previous versions. The single executable installation method is now gone. Instead all individual services have been split into their own components. To try and simplify the installation process Sitecore created an installation framework called SIF. It combines Powershell and JSON configuration files to build Sitecore environments. By doing this Sitecore have simplified DevOps and automated deployments.
Until dynamic placeholders have only been available using a Sitecore module or custom code. Sitecore 9 now has built in support.
XDB SQL Support
Sitecore 9 can now write analytics data directly to a SQL Database without going via MongoDB first. In fact the initial release of Sitecore 9 has dropped MongoDB completely, however support will be included in future releases.
Sitecore Zenith and Horizon
While its not included yet, Horizon will change the way content editors interact with Sitecore. This will replace both the Content Editor and Experience Editor with a single solution, providing full drag and drop, device emulation, heat maps and machine learning.
When creating a dynamic disk VirtualBox asks you to specify the maximum size. If the max dynamic disk size needs changing after its initial creation we cannot use the VirtualBox interface, instead we need the VBoxManage command line tool.
1. Shutdown the VM and quit VirtualBox
2. Open the Terminal app and use the following command to navigate to the VirtualBox app directory
3. Now in the proper directory, you’re ready to run the resize command with the following syntax:
VBoxManage modifyhd –resize [new size in MB] [/path/to/vdi]
VBoxManage modifyhd –resize 30000 ~/Documents/VM/Windows10.vdi
4. If desired, verify the change has taken place with the showhdinfo command:
5. Launch VirtualBox and boot renewly resized VM