Merge branch 'Content/Pointers' of https://github.com/JDSherbert/Programming_HandBook into Content/Pointers

Author: JDSherbert

404.html

@@ -0,0 +1,13 @@
+---
+layout: default
+title: 404
+permalink: /404.html
+nav_exclude: true
+search_exclude: true
+---
+
+<h1>404 - Page Not Found</h1>
+
+<p>The page/content requested could not be found. Please check the URL or use the navigation menu to find what you're looking for.</p>
+
+<p><a href="/Programming_HandBook/">Go back to the home page</a></p>

_includes/components/footer.html

@@ -3,7 +3,7 @@
 
   {% if site.back_to_top %}
     <p>
-      <a href="#top" id="back-to-top">Back to Top</a>
+      <a href="" id="back-to-top">Back to Top</a>
     </p>
   {% endif %}
 

_includes/components/search_header.html

@@ -0,0 +1,7 @@
+<div class="search" role="search">
+    <div class="search-input-wrap">
+      <input type="text" id="search-input" class="search-input" tabindex="0" placeholder="Search" aria-label="Search" autocomplete="off">
+      <label for="search-input" class="search-label"><svg viewBox="0 0 24 24" class="search-icon"><use xlink:href="#svg-search"></use></svg></label>
+    </div>
+    <div id="search-results" class="search-results"></div>
+  </div>

_includes/components/sidebar.html

@@ -26,7 +26,7 @@
     {{ nav_footer_custom }}
   {% else %}
     <footer class="site-footer">
-      Content Produced by <a href="https://github.com/VerzatileDev">VerzatileDev</a> & <a href="https://github.com/JDSherbert">JDSherbert</a>
+      An Open source project hosted at: <a href="https://github.com/VerzatileDevOrg/Programming_HandBook">Programming Handbook</a>
     </footer>
   {% endif %}
 </div>

docs/IDE/VisualStudio/ChangeProjectName.md

@@ -0,0 +1,105 @@
+---
+layout: default
+title: Change Project Name
+nav_order: 1
+parent: Visual Studio
+grand_parent: IDE
+has_children: false
+---
+
+{{ page.title }}
+======================
+
+
+## Introduction:
+
+This documentation outlines the steps to rename a project within a Visual Studio solution. Please follow the provided instructions carefully to ensure a successful project renaming process.
+
+## Steps:
+
+1. **Open Project Solution:**
+   - Open your project solution by accessing the corresponding SLN file with the repository folder.
+
+2. **Locate Files:**
+   - When inside the solution of `Visual studio``, identify the following two files within your solution directory:
+    - The top file is the Solution name (e.g., `YourProjectName.sln`, currently displayed as "Solution "name" (1 of 1 Project)").
+    - The bottom file is the Project name (e.g., `YourProjectName.vcxproj`).
+
+     As an Example Path:
+
+     -> Solution Name -> Project Name -> Files
+
+     <img src="{{ site.baseurl }}/images/VisualStudioImages/SolutionDirectory.png" alt="Solution Directory" style="width:50%;">
+
+3. **File Name Adjustment:**
+   - Change the name of the bottom file (Project name) to match the name of the top file (Solution name).
+   - Ensure both files have the same name.
+
+4. **Avoid Closing the Application:**
+   - It is crucial not to close the application during this process to prevent any potential issues.
+
+5. **Explore Project Location:**
+   - Open your project location folder and observe the files.
+   - Note that only the `.sln` file is likely to be changed at this point.
+
+    <img src="{{ site.baseurl }}/images/VisualStudioImages/OpenFolderInFileExplorer.png" alt="Open Folder In FileExplorer" style="width:50%;">
+
+    <img src="{{ site.baseurl }}/images/VisualStudioImages/ProjectFolderFilters.png" alt="Project Filters In FileExplorer" style="width:80%;">
+
+6. **Modify SLN File with Notepad:**
+   - Open the `.sln` file using Notepad.
+   - Locate and update the names in the designated areas to your desired values.
+
+   <img src="{{ site.baseurl }}/images/VisualStudioImages/SLNFile.png" alt="SLN File in NotePad" style="width:90%;">
+
+7. **Edit vcxproj File:**
+   - Open the `.vcxproj` file with Notepad.
+   - Locate the section containing the project name and ensure it matches the new name.
+
+   <img src="{{ site.baseurl }}/images/VisualStudioImages/vcxprojFile.png" alt="vcxproj File in NotePad" style="width:80%;">
+
+8. **Re-Scan Solution:**
+   - Open your `.sln` file and reload the solution to apply the changes.
+
+   <img src="{{ site.baseurl }}/images/VisualStudioImages/RescanSolution.png" alt="Rescan solution In Visual Studio" style="width:30%;">
+
+9. **Adjust Filters:**
+   - After reloading, default `filters`, may be removed.
+   - Create new filters named "Header Files," "Resource Files," and "Source Files."
+
+   <img src="{{ site.baseurl }}/images/VisualStudioImages/ProjectFilters.png" alt="Project Filters In Visual Studio" style="width:30%;">
+
+10. **Organize Elements:**
+    - Transfer each project element into the appropriate filter.
+    - Add each filter along with its corresponding file.
+
+11. **Temporary File Creation:**
+    - If necessary, create a temporary text file to facilitate the addition of filters.
+
+12. **Update vcxproj.filters:**
+    - Open the newly created file and copy its contents into `vcxproj.filters`.
+    - Save the changes.
+
+    <img src="{{ site.baseurl }}/images/VisualStudioImages/CopyOldFilterToNewFilter.png" alt="Copy old Filter to new Filter In Visual Studio" style="width:60%;">
+
+13. **Delete Unneeded Files:**
+    - Delete the unnecessary `.filter` file.
+    - Repeat the same step for the .user file, copying its data into vcxproj.user.
+
+14. **Review Changes:**
+    - Verify changes in file statuses (red for removed, green for added, yellow for changed).
+
+15. **Close and Re-Open Solution:**
+    - Close the solution and reopen it to ensure that everything functions as expected.
+
+16. **Test Functionality:**
+    - Verify that the project works correctly.
+    - If any issues arise, repeat steps from 5 onwards until the process is completed accurately.
+
+By following these steps, you should have successfully renamed your project within the Visual Studio solution, and the solution name should be displayed as "Solution `name` (1 of 1 Project)."
+
+
+---
+
+#### Author: VerzatileDev
+#### Published: 22/12/2023

docs/IDE/VisualStudio/VisualStudio.md

@@ -3,7 +3,7 @@ layout: default
 title: Visual Studio
 nav_order: 1
 parent: IDE
-has_children: false
+has_children: true
 ---
 
 {{ page.title }}

docs/Language/C++/Pointers.md

@@ -39,7 +39,8 @@ int main()
 // Value using raw pointer: 69
 ```
 
+
 ---
 
 #### Author: JDSherbert
-#### Published: 20/12/2023
+#### Published: 20/12/2023

docs/VersionControl/Git/Github.md

@@ -3,7 +3,7 @@ layout: default
 title: Github
 nav_order: 1
 parent: Version Control
-has_children: false
+has_children: true
 ---
 
 {{ page.title }}

docs/VersionControl/Git/Github/EnterpriseToPersonal.md

@@ -0,0 +1,80 @@
+---
+layout: default
+title: Transfer Enterprise to Personal Github
+nav_order: 1
+parent: Github
+grand_parent: Version Control
+has_children: false
+---
+
+{{ page.title }}
+======================
+
+## Introduction
+
+Transferring a GitHub Enterprise repository in 2023 can be accomplished through two distinct methods. This documentation outlines these methods—one utilizing GitHub's web interface entirely, and the other involving local machine command-line operations.
+
+### Method 1: GitHub Import Code
+
+This method involves utilizing GitHub's web interface to seamlessly transfer your GitHub Enterprise repository.
+
+1. **Create a New Repository in Personal GitHub Account:**
+   - Log in to your Personal GitHub account.
+   - Create a new repository and keep it empty with no Git ignore or readme files.
+   - Set the repository visibility to public.
+
+2. **Access "Import Code" Feature:**
+   - On the empty project page, scroll down to find the "Import Code" option.
+   - Click on "Import Code" to initiate the transfer process.
+
+3. **Enter GitHub Enterprise Repository Link:**
+   - In the provided field, enter your GitHub Enterprise repository link (e.g., `https://enterprise.name.ac.uk/MyProject.git`).
+   - Click "Begin Import" to commence the transfer.
+
+4. **Login to GitHub Enterprise Account:**
+   - Enter your GitHub Enterprise account credentials when prompted.
+
+5. **Select Project for Import:**
+   - A panel will display projects associated with your Enterprise URL.
+   - Choose the specific project you want to transfer and click "Submit."
+
+6. **Monitor Import Progress:**
+   - Track the progress of the import operation.
+
+7. **Completion Notification:**
+   - Once the transfer is complete, an email notification will be sent.
+   - The email will contain a link to your new repository page.
+
+### Method 2: Local Command-Line Operation
+
+For those preferring a local approach, follow these command-line steps:
+
+1. **Create a New Repository in Personal GitHub Account:**
+   - Log in to your Personal GitHub account.
+   - Create a new repository and keep it empty with no Git ignore or readme files.
+   - Set the repository visibility to public.
+
+
+2. **Configure Local Repository:**
+   - In the command line, navigate to your local copy of the Enterprise repository.
+   - Ensure it's up-to-date using `git checkout master` and `git pull origin master` (or your desired branch).
+
+
+3. **Add New Repository as Remote:**
+   - Run the command: `git remote add public https://github.com/user/repo.git` (replace with your new repository URL).
+
+
+4. **Force Push to New Repository:**
+   - Perform a force push to your new repository: `git push -f public`
+
+By choosing between the web-based GitHub Import Code method or the local command-line approach, you can efficiently transfer your GitHub Enterprise repository, preserving contributors, issues, and project history.
+
+
+### References
+
+For additional information, you may refer to the [GitHub Importer Documentation](https://docs.github.com/en/migrations/importing-source-code/using-github-importer/importing-a-repository-with-github-importer).
+
+---
+
+#### Author: VerzatileDev
+#### Published: 22/12/2023