{"id":257480,"date":"2026-10-26T05:00:10","date_gmt":"2026-10-26T12:00:10","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=257480"},"modified":"2026-10-14T11:11:09","modified_gmt":"2026-10-14T18:11:09","slug":"keep-your-investigation-between-sessions","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/keep-your-investigation-between-sessions\/","title":{"rendered":"Keep your investigation between sessions"},"content":{"rendered":"

A bug investigation often starts with a few notes: what you tried, which input reproduced the problem, and what you want to check next. You might not be ready to choose a filename or add those notes to a project. You still want them there when you return.<\/p>\n

In Visual Studio 2026 version 18.11, you can create a standalone Markdown file from New File<\/strong> and use the opt-in Hot Exit preview feature to resume that unfinished note after closing and reopening Visual Studio. Start the note while the details are fresh, then return to it next session.<\/p>\n

Start the note without adding a project item<\/h2>\n
    \n
  1. Press Ctrl<\/kbd> + N<\/kbd> to open New File<\/strong>.<\/li>\n
  2. Select Markdown File<\/strong>.<\/li>\n
  3. Select Open<\/strong> and start writing.<\/li>\n<\/ol>\n

    \"New<\/p>\n

    This is separate from Add New Item<\/strong>, which creates a project item. The original feedback<\/a> specifically asked for a Markdown template in New File<\/strong>, including when working without an open solution.<\/p>\n

    The Markdown editor itself isn’t new in this release. You can use it to turn your notes into headings, lists, and fenced code blocks, then check the rendered result. The Markdown preview guide<\/a> explains its editing and preview controls.<\/p>\n

    Resume the same unfinished note<\/h2>\n

    Hot Exit is off by default. To enable it, go to Tools<\/strong> > Options<\/strong>, expanding All Settings<\/strong> > Projects and Solutions<\/strong> > General<\/strong>, and selecting Reopen unsaved documents on solution load or empty environment<\/strong>.<\/span><\/p>\n

    With Hot Exit enabled, closing Visual Studio preserves session state. When you reopen Visual Studio, it restores open documents and unsaved edits, including new files you haven’t saved yet. Your note can remain unfinished without forcing you to choose a permanent home for it before you close the IDE.<\/p>\n

    \"Visual<\/p>\n

    Hot Exit also preserves changes to previously saved files, your tab and window layout, and undo functionality for saved files. For those saved files, you can continue using Ctrl<\/kbd> + Z<\/kbd> after restoring the session.<\/p>\n

    This is session preservation, not the same thing as deliberately saving a document to disk or committing it to source control. Save the note when you want to share it or keep it as part of the repository. The useful choice here is that a temporary note doesn’t have to become a project artifact merely to survive a normal close and reopen.<\/p>\n

    The Hot Exit request<\/a> calls out exploratory work and temporary files as reasons to preserve unsaved documents. Keep the preview option off if you prefer your current close-and-save workflow.<\/p>\n

    Try the combination with a disposable investigation note: write down the next thing to check, close Visual Studio with Hot Exit enabled, and reopen it to continue the note.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Start a standalone Markdown note and use the opt-in Hot Exit preview to resume unsaved work next session.<\/p>\n","protected":false},"author":68130,"featured_media":257473,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[155],"tags":[],"class_list":["post-257480","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-visual-studio"],"acf":[],"blog_post_summary":"

    Start a standalone Markdown note and use the opt-in Hot Exit preview to resume unsaved work next session.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/257480","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/users\/68130"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=257480"}],"version-history":[{"count":1,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/257480\/revisions"}],"predecessor-version":[{"id":257510,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/257480\/revisions\/257510"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/257473"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=257480"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=257480"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=257480"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}