<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Lawrence Eze on Medium]]></title>
        <description><![CDATA[Stories by Lawrence Eze on Medium]]></description>
        <link>https://medium.com/@ifeanyilawrence?source=rss-fc6aabe27213------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uJMMsviroYP-xuugmBn_0g.jpeg</url>
            <title>Stories by Lawrence Eze on Medium</title>
            <link>https://medium.com/@ifeanyilawrence?source=rss-fc6aabe27213------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 06:29:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ifeanyilawrence/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Setup/Run .Net Core Applications and MSSQL Server On macOS]]></title>
            <link>https://medium.com/@ifeanyilawrence/setup-run-net-core-applications-and-mssql-server-on-macos-f055b570c35b?source=rss-fc6aabe27213------2</link>
            <guid isPermaLink="false">https://medium.com/p/f055b570c35b</guid>
            <category><![CDATA[vscode]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[mssql]]></category>
            <category><![CDATA[aspnetcore]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Lawrence Eze]]></dc:creator>
            <pubDate>Fri, 03 Apr 2020 12:29:06 GMT</pubDate>
            <atom:updated>2020-04-03T12:29:06.121Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Setup/Run .Net Core Applications and MSSQL Server On macOS</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tZA5Dnr-dbE0pPUih4FjgQ.png" /></figure><p>It is no news that .Net Core gives you a fast and modular platform for creating applications that run on Windows, Linux, and macOS. Visual Studio Code (VSCode) and Microsoft Visual Studio For Mac can be used to develop .Net Core applications on the macOS. The major problem has always been running a MSSQL server which your application can connect to on the macOS. This issue of running the MSSQL server can be solved by running a docker image of the MSSQL server. I will show how to do this in this writeup, as well as how to run an already existing .NET Core application on macOS using VSCode and Visual Studio for Mac.</p><ol><li><strong>Running And Connecting To MSSQL Server on Mac</strong></li></ol><p>To run the MSSQL server using a docker image, ensure you have already installed docker on your machine. You can check for docker installation by typing docker on the terminal, if docker has been installed, it will pop out usage information and options for you.</p><p>After installing docker, run the following command on the terminal:</p><figure><img alt="docker command for running mssql-server instance" src="https://cdn-images-1.medium.com/max/1024/1*PB75mOe20FJQ0KSszC8bZA.png" /></figure><p>This will startup a local mssql-server instance running as the SQL Express edition on port 1433. Replace the password part with your chosen strong password. To avoid password validation failures, the password must meet SQL Server password policy requirements( the password must be at least 8 characters long and contain characters from three of the following four sets: Uppercase letters, Lowercase letters, Base 10 digits, and Symbols..).</p><p>If the mssql image exists on your system, the above command will run the mssql-server instance in detached mode. To run the instance in an interactive mode (showing logs), use the below command:</p><figure><img alt="docker command for running mssql-server instance" src="https://cdn-images-1.medium.com/max/1024/1*7KWO9UK1JaAQh2Ra0ShSxg.png" /></figure><p>If the image is not on your system, it will be downloaded from dockerhub before running. For more details about the MSSQL image, visit this link: <a href="https://hub.docker.com/_/microsoft-mssql-server">https://hub.docker.com/_/microsoft-mssql-server</a>.</p><p>For connecting to the running mssql server and performing db operation, you can use the terminal or download any GUI that supports mssql server. One that is free and easy to use is DBeaver (download from <a href="https://dbeaver.io/download/">https://dbeaver.io/download/</a>). The connection for DBeaver can be seen below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pqt_4mI4jJdw9gLqIs5-xg.png" /></figure><p><strong>2. Running .Net Core application using VSCode on macOS</strong></p><p>To run your already existing .Net Core application on VSCode, first ensure you have the required sdk for the given version of .Net Core on which your application was built on.</p><p>After downloading and installing the sdk open the project using VSCode on your Mac. On opening the project, VSCode will start downloading the C# and .Net extensions. Once done, use the dotnet restore and dotnet build command to restore the packages and build each project. Ensure you are on the directory of the project before running the command. If the sdk on which a given project runs is not installed, it will throw errors at this point.</p><p>Modify your connection string as follows in order to connect to the instance of MSSQL Server that is running on the Docker container:</p><figure><img alt="connectionString" src="https://cdn-images-1.medium.com/max/1024/1*34KlmxtX3itJgw1bcitRVg.png" /></figure><p>Then run your application using the dotnet run command. You can access your application using localhost and the port as set in your launchSettings.json file.</p><p><strong>3. Running .Net Core application using Visual Studio for Mac</strong></p><p>To run your .Net Core application on macOS using Visual Studio for Mac, after installation of Visual Studio for Mac and installing the necessary dependencies (visit this link for the system requirements: <a href="https://docs.microsoft.com/en-us/visualstudio/productinfo/vs2019-system-requirements-mac">https://docs.microsoft.com/en-us/visualstudio/productinfo/vs2019-system-requirements-mac</a>), open the project, allow the packages to be restored, build and run your application. Remember to update your connection string as shown above.</p><p>Thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f055b570c35b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Could not find iPhone simulator after migrating from Xcode10 to Xcode11; React Native]]></title>
            <link>https://medium.com/@ifeanyilawrence/could-not-find-iphone-simulator-after-migrating-from-xcode10-to-xcode11-react-native-267ed0928cc7?source=rss-fc6aabe27213------2</link>
            <guid isPermaLink="false">https://medium.com/p/267ed0928cc7</guid>
            <category><![CDATA[xcode11]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Lawrence Eze]]></dc:creator>
            <pubDate>Tue, 19 Nov 2019 09:24:51 GMT</pubDate>
            <atom:updated>2019-11-19T09:34:34.251Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*gam56-AtNkK6MN74v4Nd-Q.png" /><figcaption>xcode-react-native</figcaption></figure><p>Developers using older versions of react-native after upgrading from Xcode10 to Xcode11 are not able to run the iphone simulator on their mac. This can be annoying and stressful to debug, knowing that few minutes ago before the upgrade everything was fine. Sometimes, you wouldn’t even know where to start debugging.</p><p>After the upgrade, their was a slight change in the simulator properties, hence, the program is not able to find and use the simulator, thereby throwing “Could not find iPhone simulator error”.</p><p>To resolve this, goto the following path on your project: node_modules/react-native/local-cli/runIOS, then open the findMatchingSimulator.js file. On line 43 or so ensure the code block is same as this:</p><p><em>if</em> (!version.includes(‘iOS’) &amp;&amp; !version.includes(‘tvOS’)) {</p><p><em>continue</em>;</p><p>}</p><p>Also where it is checking the simulator availability, around line 55, change the check for isAvailable from “YES” to true as seen below:</p><p><em>if</em> (simulator.availability !== ‘(available)’ &amp;&amp; simulator.isAvailable !== true){</p><p><em>continue</em>;</p><p>}</p><p>Save the file and run start the simulator again (yarn ios or npm run ios as the case may be).</p><p>If you are experiencing the “Could not find iPhone X simulator error”, this is because iPhone X is used as default and maybe from your xcode, the iPhone X simulator is not installed. You can specify the the simulator version on the script session of your package.json file for ios as seen below:</p><p>“scripts”: {</p><p>“ios”: “react-native run-ios — simulator=’iPhone 11&#39;”</p><p>}</p><p>Thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=267ed0928cc7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Postman Archived Collections]]></title>
            <link>https://medium.com/@ifeanyilawrence/postman-archived-collections-2392a9ff5fa7?source=rss-fc6aabe27213------2</link>
            <guid isPermaLink="false">https://medium.com/p/2392a9ff5fa7</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[api-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[postman]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Lawrence Eze]]></dc:creator>
            <pubDate>Fri, 04 Oct 2019 13:43:27 GMT</pubDate>
            <atom:updated>2019-10-04T13:56:40.828Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tO_SemO2SWDsmN1bzIwmcA.png" /></figure><p><strong>Postman Archived Collections</strong></p><p>Have you ever created more collections in your free postman account for a team workspace and your collections got archived without you having access to it? Most people will say, you can easily build up the collections again. But most times, you have already done many environmental configuration and settings like saving your token to an environmental variable with javaScript (on successful authentication), so that you wouldn’t need to manually enter it on subsequent requests that require authentication. Setting everything up again can be hectic, especially if you don’t want to upgrade your postman account to premium or enterprise.</p><p>So, the good news is that there is a way you can get your collections back without having to go to the postman page to request for the data (which is not working, as at the time of this write-up).</p><p>To get those collections back, click on the file menu and from there, select settings, then under data tab, click on the download button under the export section; this downloads all your collections, the team archived collections inclusive. You can then import the exported collections skipping the already existing ones or adding them as a copy(and removing the duplicate afterwards).</p><p>The best way is always to upgrade. Give them credit for the wonderful work and pay for the value it is bringing. I hope this becomes useful to someone someday.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2392a9ff5fa7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>