<p>The new awesome <kbd>Ctrl</kbd> + <kbd>.</kbd> keyboard shortcut to show smart tags has suddenly stopped working, a week or so after I discovered it :( </p>

<p>I am missing it badly, having had to revert back to <kbd>Ctrl</kbd> + <kbd>Alt</kbd> + <kbd>F10</kbd>, which really just isn't the same.</p>

<p>I recently installed F# CTP 1.9.6.2</p>

<p>Has anyone else</p>

<ul>
<li>installed this CTP and still has <kbd>Ctrl</kbd> + <kbd>.</kbd></li>
<li>Lost <kbd>Ctrl</kbd> + <kbd>.</kbd> without installing F#</li>
<li>Even better, found how to get it back again?</li>
</ul>

<p><strong>EDIT</strong> In attempting John Sheehan recommendation, I have noticed that my available mapping schemes only include <code>Visual C# 2005</code>, should I not have a 2008?</p>

<p>Also the mapped shortcut to this is</p>

<pre><code>OtherContextMenus.FSIConsoleContext.CancelEvaluation
</code></pre>

From the
documentation
:
Use of NSCalendarDate strongly
  discouraged. It is not deprecated yet,
  however it may be in the next major OS
  release after Mac OS X v10.5. For
  calendrical calculations, you should
  use suitable combinations of
  NSCalendar, NSDate, and
  NSDateComponents, as described in
  Calendars in
Dates and Times
  Programming Topics for Cocoa
.
Following that advice:
```
```
NSDate *today = [NSDate date];

NSCalendar *gregorian = [[NSCalendar alloc] initWithCalendarIdentifier:NSGregorianCalendar];

NSDateComponents *components = [[NSDateComponents alloc] init];
components.day = 1;
NSDate *tomorrow = [gregorian dateByAddingComponents:components toDate:today options:0];
[components release];

NSUInteger unitFlags = NSYearCalendarUnit | NSMonthCalendarUnit |  NSDayCalendarUnit;
components = [gregorian components:unitFlags fromDate:tomorrow];
components.hour = 0;
components.minute = 0;

NSDate *tomorrowMidnight = [gregorian dateFromComponents:components];

[gregorian release];
[components release];
```
```
(I'm not sure offhand if this is the most efficient implementation, but it should serve as a pointer in the right direction.)
Note: In theory you can reduce the amount of code here by allowing a date components object with values greater than the range of normal values for the component (e.g. simply adding 1 to the day component, which might result in its having a value of 32). However, although
```
dateFromComponents:
```
may
tolerate out-of-bounds values, it's not guaranteed to.  You're strongly encouraged not to rely on it.