<?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 Semih Ünal on Medium]]></title>
        <description><![CDATA[Stories by Semih Ünal on Medium]]></description>
        <link>https://medium.com/@ssemihunal?source=rss-acfd8a48a386------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*SsdJZMNGZKd_KVDPgnD-IA.jpeg</url>
            <title>Stories by Semih Ünal on Medium</title>
            <link>https://medium.com/@ssemihunal?source=rss-acfd8a48a386------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:36:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ssemihunal/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[What is GitHub Actions / Workflows?]]></title>
            <link>https://medium.com/insiderengineering/what-is-github-actions-workflows-f373d9037981?source=rss-acfd8a48a386------2</link>
            <guid isPermaLink="false">https://medium.com/p/f373d9037981</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[action]]></category>
            <category><![CDATA[eslint]]></category>
            <category><![CDATA[github-actions]]></category>
            <category><![CDATA[github-workflow]]></category>
            <dc:creator><![CDATA[Semih Ünal]]></dc:creator>
            <pubDate>Mon, 31 Jul 2023 07:01:55 GMT</pubDate>
            <atom:updated>2023-12-29T11:54:22.183Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is GitHub Actions?</h3><blockquote><em>In this article, I will try to provide information and show some examples about GitHub Actions, which we frequently use in project development and deployment processes at Insider.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*U56JIjUVBUVcUZRTA8RBXA.png" /><figcaption><strong>GitHub Actions</strong></figcaption></figure><p>GitHub Actions is a feature of GitHub. GitHub Actions is a CI/CD platform that allows developers to automate the process of building, testing, and deploying their applications.</p><figure><img alt="github-actions" src="https://cdn-images-1.medium.com/max/897/1*D7wPGeRAFBmm7CyOmKh6WA.png" /><figcaption><strong>When we open the repository, we can see the Actions tab.</strong></figcaption></figure><p>With GitHub Actions, developers can define workflows that describe how their code should be built, tested, and deployed. These workflows can be triggered automatically based on certain events, such as code pushes or pull requests.</p><p>By using GitHub Actions, Time can be saved and errors reduced by automating repetitive tasks. For example, a workflow can be created to automatically build and test the code every time a pull request is created.</p><p><strong>Workflow</strong> is a YAML file that defines a set of actions that should be performed automatically when a certain event occurs within a project.</p><h3>How to create GitHub Action?</h3><p>First of all, to create a GitHub action for our project;</p><ol><li>Create a .github/workflows directory in your project.</li><li>In this directory, create a .yml file. Edit the file to define the properties of your GitHub Action workflow.</li><li>Finally, upload the file to GitHub by committing and pushing.</li></ol><pre>name: learn-github-actions<br>on:<br>  push:<br>    branches:<br>      - main<br>jobs:<br>  build:<br>    runs-on: ubuntu-latest<br>    steps:<br>    - name: Checkout code<br>      uses: actions/checkout@v2<br>    - name: Install dependencies<br>      run: npm install<br>    - name: Run tests<br>      run: npm test</pre><h4>The basic components of GitHub Actions workflows</h4><ul><li><strong>on: </strong>Allows this action to be triggered when any event occurs within the project. (pull_request, push)</li><li><strong>runs-on: </strong>Determines which operating system the job will run on. (ubuntu-latest, windows-latest, macos-latest)</li><li><strong>jobs: </strong>Used to define one or more jobs within a workflow.</li><li><strong>steps: </strong>Defines the specified steps to perform the job.</li><li><strong>cancel-in-progress:</strong> While a GitHub Action is in progress, running the same action again can cancel the previous instance of the action.</li></ul><h3><strong>Frequently Used GitHub Actions in Our Projects</strong></h3><p>Some of the GitHub actions we frequently use in our projects at Insider include “eslint”, “test &amp; coveralls”, “npm publish”, and “release”.</p><p>For example, in many of our projects, “eslint” and “test &amp; coveralls” workflows run for every code push.</p><p>Additionally, for our npm package projects, “npm publish” runs when pushed to the master branch.</p><h4><strong><em>1. Eslint Workflow</em></strong></h4><ul><li><strong>Eslint</strong> is a tool that identifies and reports errors in your JavaScript codes.</li><li>Using the ESLint flow improves the code quality of the project and allows developers to write better-quality code by detecting bugs and problems in their code early on.</li></ul><blockquote><strong>Integrating ESLint workflow step by step into the project.</strong></blockquote><p>First, let’s create a <strong>eslint.yml<em> </em></strong>file in the <strong>.github/workflows</strong> directory. (This file will define the configuration for Git Action.)</p><ol><li>In the <strong>eslint.yml</strong> file, let’s define the action name using the name key;</li></ol><pre>name: ESLint Check</pre><p>3. Then, define the trigger for the action using the <strong>on</strong> key. In this case, we want the action to run on any push to the repository.</p><pre>on: push</pre><p>4. Define the jobs that the action will perform using the key <strong>jobs</strong>. For this case, we will create a <strong>job</strong> named eslint that runs the <strong>eslint</strong> command in the project files:</p><pre>name: &quot;ESLint Check&quot;<br>on: push<br>jobs: <br>  eslint: <br>    runs-on: ubuntu-latest<br>    steps:<br>    - uses: actions/checkout@v2<br>    - name: Use Node.js<br>      uses: actions/setup-node@v2<br>      with: <br>        node-version: &quot;14.x&quot;<br>    - name: Install Dependencies <br>      run: npm install<br>    - name: Run ESLint<br>      run: npm run eslint<br>concurrency:<br>  group: eslint-check-${{ github.event.pull_request.number || github.ref }}<br>  cancel-in-progress: true</pre><p>-&gt; Now let me explain step by step the work we do in the jobs section.</p><ol><li>Firstly, we checkout the repository using the <strong>actions/checkout<em> </em></strong>action.</li><li>Next, we set up Node.js environment using<strong><em> </em></strong><strong>actions/setup-node@v2<em> </em></strong>action.</li><li>Then, we install the project dependencies using <strong>npm install</strong>.</li><li>Finally, we run the ESLint command using <strong>npm run eslint .</strong></li></ol><p>Then, when we push our code to GitHub, we can see the eslint action we created in the Action tab.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/947/1*uzVsCVqJ3xycyMa8XWXOEA.png" /><figcaption>Eslint Workflow</figcaption></figure><p>As seen in the picture, the eslint action failed. In this case, we can click on the item to see where the error originated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/581/1*GO3-K6Oif4e4qNdLOegqZg.png" /><figcaption>Eslint Errors</figcaption></figure><p>For example, in this case, we have 2 errors due to missing semicolons and unnecessary spaces. In order for this action to be successful, we need to fix the errors in our code.</p><p>When we fix our code and push it again, we can see that the second eslint action was successful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/945/1*YN7DBkcZ_4EPMVIJwp1_Pg.png" /><figcaption>Failed and Successful Git Workflows</figcaption></figure><p>In this way, we can add the eslint tool to the project and automate it with the GitHub action feature, preventing possible errors and maintaining our code quality.</p><h4>2. Tests and Coveralls</h4><p>One of the most frequently used git actions is “tests &amp; coveralls”. When we include this action in our project, it gives us:</p><ul><li><strong>Run tests automatically:</strong> The <strong>Tests and Coveralls</strong> action allows a project’s tests to run automatically. This allows developers to use their time more efficiently, rather than manually running each test.</li><li><strong>Measuring Test Coverage: </strong>This action also measures and reports test coverage.</li></ul><p><em>( </em><strong><em>Test coverage</em></strong><em> indicates which code of a project is being tested and which is not. This allows developers to identify their missing tests and better test their code. )</em></p><ul><li><strong>Coveralls.io Integration: </strong>This action runs the tests, generates coverage reports, and then sends these reports to the Coveralls.io tool. Coveralls.io tool enables us to monitor our project’s coverage performance.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/877/1*xVV1R8NU_Ih0jN2Ih9onfw.png" /><figcaption>coveralls.io</figcaption></figure><p>As seen in the image above, with the help of this tool, we can see the branch, commit, and percentage of coverage information of the pushed code every time it is pushed.</p><p>Thus, we control the codes that reduce the coverage value.</p><blockquote><strong>Integrating Tests and Coveralls workflow step by step into the project.</strong></blockquote><p>Let’s create a <strong>tests-and-coveralls</strong> file in the <strong>.github/workflows</strong> directory to add this action to our project.</p><p>Then, let’s add the following code to our file.</p><pre>name: Tests and Coveralls<br>on:<br>  push:<br>    branches-ignore:<br>      - master<br>jobs:<br>  test:<br>    runs-on: ubuntu-latest<br>    strategy:<br>      matrix:<br>        node-version: [14.x]<br>    steps:<br>    - uses: actions/checkout@v2<br>    - name: Use Node.js ${{ matrix.node-version }}<br>      uses: actions/setup-node@v1<br>      with:<br>        node-version: ${{ matrix.node-version }}<br>    - run: npm install<br>    - run: npm run test -- --coverage<br>    - uses: CoverallsApp/github-action@master<br>      with:<br>        github-token: ${{ secrets.GITHUB_TOKEN }}</pre><ul><li>First, the repo is cloned and node.js is installed.</li><li>The dependencies are installed with the <strong>npm install</strong> command.</li><li>The <strong>npm test -- --coverage</strong> command runs unit tests and reports code coverage.</li><li>In the final step, coverage report results are sent to the <strong>coveralls.io</strong> tool using <strong>CoverallsApp/github-action.</strong></li></ul><p>When we push our code in this way, we can now see that 2 actions are running in our project.</p><p>When we pushed our first time, the action we created failed because of an error in our unit tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/989/1*RZA1mSjfTflWcqXE0PBpIg.png" /><figcaption>Tests and Coveralls action failed</figcaption></figure><p>After fixing the failed unit tests, I pushed again and eslint and unit test action were successful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/983/1*9QWTpBRuSMz1SeyFgSWFpA.png" /><figcaption>All actions passed successfully</figcaption></figure><p>Before using this action, we had to manually check the unit tests and coverage values every time we created pull requests. This could increase the risk of incorrect tests or incomplete tests going live or being overlooked. Additionally, we couldn’t automatically report our project’s coverage values.</p><p>However, with this action, our tests are automatically run after every code change, and coverage values are reported. This way, we can be sure that the unit tests are written correctly and completely.</p><blockquote>In this way, every time we push our code, eslint and test actions will run automatically and we can easily see when there is a problem.</blockquote><h4>3. Publish To NPM</h4><p>In this example, we have an <strong>NPM</strong> package project that works with webpack. We need to build our code and publish it to npm when we push the code to the master branch.</p><p>We can automate this publish process by creating a workflow.</p><p>Let’s first create a <strong>publish-to-npm.yml </strong>file under the <strong>.github/workflows</strong> directory and add this code.</p><pre>name: Publish NPM Package<br>on:<br>  push:<br>    branches:<br>      - master<br><br>env:<br>  NODE_AUTH_TOKEN: ${{ secrets.NPMJS_ACCESS_TOKEN }}<br><br>jobs:<br>  publish_npm_package_and_create_release:<br>    runs-on: ubuntu-latest<br>    permissions: write-all<br>    steps:<br>      - name: Checkout Code<br>        uses: actions/checkout@v2<br><br>      - name: Set up Node.js<br>        uses: actions/setup-node@v3<br>        with:<br>          node-version: &#39;16.x&#39;<br>          registry-url: &#39;https://registry.npmjs.org&#39;<br><br>      - name: Install Dependencies<br>        run: npm install<br><br>      - name: Build<br>        run: npm run build<br><br>      - name: Publish NPM Package<br>        run: npm publish</pre><p>This action is triggered when we push code to the master branch, and the associated steps are executed.</p><ul><li>The repository is cloned, and Node.js is installed.</li><li>After that, dependencies are installed.</li><li>After that, the project is built using the <strong>npm run build</strong> command.</li><li>Finally, our package is sent to NPM with the <strong>npm publish</strong>command.</li></ul><p>When we push the code, we can see that the <strong>Publish to Npm</strong> action is triggered in the actions tab.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/982/1*oghg76ixZPw_9PKYiX2Mrw.png" /><figcaption>Publish to Npm action passed successfully</figcaption></figure><p>When the Release action is successful, we will see that our package is updated on npm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*CInJq5L7egzwrktz1q_iTg.png" /><figcaption><a href="https://www.npmjs.com/">https://www.npmjs.com/</a></figcaption></figure><p>Finally we check npm and we can see that our package has successfully arrived to npm.</p><p>Before using this action, we were merging our code into the master branch when our project was ready to go live, and manually building our project and running the <strong>npm login</strong> and <strong>npm publish</strong> commands.</p><p>However, with this action, when our code is ready to go live, it will automatically build our project and publish our npm package with its new version.</p><h4>4. Release</h4><p><strong>Release action</strong> is a GitHub Action used to release a new version for a project. This action lets you create a new release, tag it, and upload it to the GitHub Releases page.</p><p>In this way, project users can easily follow new releases.</p><p>We can create a release using the <strong>create-release</strong> action in our project. For this, it is sufficient to add the following code to the step area of our yaml file.</p><pre>- name: Create Release<br>  id: create_release<br>  uses: actions/create-release@v1<br>  env:<br>    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}<br>  with:<br>    tag_name: v1.0.0<br>    release_name: Release v1.0.0<br>    draft: false<br>    prerelease: false</pre><p>In this example, Release’s name is <strong>Release v1.0.0.</strong> and its tag is set to <strong>v1.0.0.</strong></p><p>Also, if we want our release to be created as a draft or prerelease, we need to set the related property to true.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9dmOjeBlaXJosDNDGMgxUA.png" /><figcaption><a href="https://github.com/">https://github.com/</a></figcaption></figure><p>So every time create-release is triggered, a new release will be added to the release page.</p><h4>Conclusion</h4><p>We have currently integrated 4 actions into our project. These are:</p><ul><li>Eslint</li><li>Tests &amp; Coveralls</li><li>Publish to Npm</li><li>Release</li></ul><p>All of these steps are essential to improve the quality of your project and provide a better development experience.</p><p>Eslint will check the quality of our code, while<strong>tests &amp; coveralls</strong> will check the accuracy of our tests and whether our code works. Then, every time our code push to master, our package will be automatically built and published on npm. Thanks to our release action, a release will be created and tagged for our current code on github.</p><p>Overall, GitHub Actions is a powerful tool that can be used to automate many aspects of software development, from testing and deployment to release management and beyond, making our life quite easy.</p><p>If you enjoyed this blog post, you may also like to read the following one.</p><p><a href="https://medium.com/insiderengineering/how-we-migrated-to-vue-3-b52887e56818">How we migrated to Vue 3</a></p><h4>Contact</h4><p>If you have any questions or feedback, feel free to reach out to me on LinkedIn. I’d be happy to hear from you! Thanks for reading!</p><p>LinkedIn: <a href="https://www.linkedin.com/in/semih-%C3%BCnal-08692713b/">semihunal</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f373d9037981" width="1" height="1" alt=""><hr><p><a href="https://medium.com/insiderengineering/what-is-github-actions-workflows-f373d9037981">What is GitHub Actions / Workflows?</a> was originally published in <a href="https://medium.com/insiderengineering">Insider One Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Counting All File Count in Directory using C# Programming Language]]></title>
            <link>https://medium.com/@ssemihunal/counting-all-file-count-in-directory-using-c-programming-language-9ff8f09da43f?source=rss-acfd8a48a386------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ff8f09da43f</guid>
            <category><![CDATA[file-counting]]></category>
            <category><![CDATA[csharp-practice]]></category>
            <category><![CDATA[counting-files-in-folder]]></category>
            <category><![CDATA[finding-count-files]]></category>
            <category><![CDATA[counting-files-in-csharp]]></category>
            <dc:creator><![CDATA[Semih Ünal]]></dc:creator>
            <pubDate>Sun, 27 Jan 2019 12:18:26 GMT</pubDate>
            <atom:updated>2019-01-27T12:42:41.302Z</atom:updated>
            <content:encoded><![CDATA[<h3>Finding All File Count in Directory using C# Programming Language</h3><p>In this Article, we’ll learn how to calculate files count in directory which want</p><p>Firstly, You have to add to your code “<strong>using System.IO</strong>” namespace</p><p>Later, There are some function that you have to know.</p><p>One of them is Directory.GetFiles(path) : This function give string array of names of files in Directory which name is “path”</p><p>Other Function is Directory.GetDirectories(path) : This function give paths of folders in directory as type of string array</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/877/1*LhhUXzU68EBp_O9WBrr1XQ.png" /></figure><p>When You looked the Above Function, you’ll understand that function was a recursive !</p><p>See you …</p><p><a href="https://github.com/unalsemih"><strong>https://github.com/unalsemih</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ff8f09da43f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[C# ile Dizindeki Dosya Sayısını Bulma]]></title>
            <link>https://medium.com/@ssemihunal/c-ile-dizindeki-dosya-say%C4%B1s%C4%B1n%C4%B1-bulma-6e299775e928?source=rss-acfd8a48a386------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e299775e928</guid>
            <category><![CDATA[semih-unal]]></category>
            <category><![CDATA[csharp]]></category>
            <category><![CDATA[csharp-ile-dosya-sayısı]]></category>
            <category><![CDATA[csharp-dosya-sayısı-bulma]]></category>
            <category><![CDATA[dizindeki-dosya-sayısı]]></category>
            <dc:creator><![CDATA[Semih Ünal]]></dc:creator>
            <pubDate>Sat, 26 Jan 2019 22:54:22 GMT</pubDate>
            <atom:updated>2019-01-26T22:54:22.504Z</atom:updated>
            <content:encoded><![CDATA[<p>Bu yazımızda C # kullanarak girilen ya da gösterilen dizindeki dosya sayısını bulacağız.</p><p>Öncelikle yazacağımız kodun çalışabilmesi için <strong><em>, using Sytem.IO</em></strong> isim uzayını eklememiz gerekmektedir.</p><p>Daha sonra bilmemiz gereken bazı fonksiyonlar bulunmaktadır. Bu fonksiyonlardan bir tanesi</p><p><strong>Directory.GetFiles(path) : Bu fonksiyon path isimli dizindeki dosyaların isimlerinin dizisini (string dizi tipinde) döndürmektedir. Haliyle herhangi bir dizinin eleman sayısını bulduğumuz gibi aynı yolla dosya sayısını bulabiliriz.</strong></p><p>Bilmemiz gereken diğer fonksiyon ise</p><p><strong>Directory.GetDirectories(path) : </strong>Bu fonksiyon ise dizin içindeki klasörlerin dizinlerini bir string dizi tipinde geri döndürmektedir.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*AbM-Xq8JhaJq0ZbNq3A5AQ.png" /></figure><p>Kodumuza baktığımızda dizin içindeki dizinleri tek tek gezinerek rekursive bir fonksiyon oluşturarak toplam dosya sayısına ulaştığımız anlaşılmaktadır.</p><p>Görüşmek Üzere …</p><p><a href="https://github.com/unalsemih">https://github.com/unalsemih</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e299775e928" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Local Ağda MSSQL Server Erişimi]]></title>
            <link>https://medium.com/@ssemihunal/local-a%C4%9Fda-mssql-server-eri%C5%9Fimi-7234fa246eeb?source=rss-acfd8a48a386------2</link>
            <guid isPermaLink="false">https://medium.com/p/7234fa246eeb</guid>
            <category><![CDATA[mssql-server-erişimi]]></category>
            <category><![CDATA[local-ağda-mssql-erişimi]]></category>
            <category><![CDATA[csharp-ile-mssql-server]]></category>
            <category><![CDATA[local-mssql-kullanımı]]></category>
            <category><![CDATA[local-ağda-mssql-server]]></category>
            <dc:creator><![CDATA[Semih Ünal]]></dc:creator>
            <pubDate>Sat, 26 Jan 2019 22:15:12 GMT</pubDate>
            <atom:updated>2019-01-26T22:15:12.305Z</atom:updated>
            <content:encoded><![CDATA[<p>Local Ağda MSSQL Server Erişimi</p><p><strong>1.</strong> SQL Server Configuration Manager’da SQL Server Network Configuration başlığını genişlettik. Ve <strong>“ Protocols for SQLEXPRESS “</strong> (SQLEXPRESS:Sunucumun Adı) üzerine tıkladık. Sağ tarafta bulunan TCP/IP protokolüne sağ tıklayıp özellikleri seçtik.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/410/1*_hiz0kgIugQXHsOkYyzm6A.png" /></figure><p>“IP Addresses” Sekmesinde SQaLSERVER’imiza erişmesini istediğimiz IP ‘lerin Enabled özelliğini ‘yes’ yaptık ve TCP Port larına 1433 yazdık.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/687/1*vTiQRcz0Rozmy264YQIPcA.png" /></figure><p>Ve Tamam dedikten sonra <strong>“ SQL Server Services “</strong> den <strong>“ SQL Server “</strong> ı sağ tıklayıp <strong>“ Restart “</strong> tıkladık. Serverımızı yeniden başlatmış olduk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/682/1*2ru7CrYdrS-ZIevkhTPYEQ.png" /></figure><p><strong>2.</strong> Bilgisayarımızın SQLSERVER ına Local Ağdaki diğer bilgisayarların engellenmeden erişebilmesi için <strong>“Windows Güvenlik Duvarı”</strong> nı açalım.Windows Güvenlik Duvarında <strong>“Yeni Bir Kural Oluştur”</strong> a tıkladık.</p><pre>Denetim Masası &gt; Sistem ve Güvenlik &gt; Windows Güvenlik Duvarı &gt; Gelişmiş Ayarlar &gt; Gelen Kuralları &gt; Yeni Kural</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MJ3Lxr0BKibtq9NFnDe39Q.png" /></figure><p><strong>*</strong>Kural Türü olarak ”<strong>Bağlantı Noktası</strong>” nı seçip “<strong>ileri</strong>” butonuna tıkladık.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*JAriqVrQC_yiHbBSnqmhQw.png" /></figure><p>Sonra Protokol olarak TCP seçtik ve Belirli Yerel bağlantı noktaları kısmını seçerek verilen textbox a <strong>1433 </strong>port numarasını yazdık ve <strong>İleri(Next) </strong>butonuna tıkladık.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*ah9epiO0RI6Vogz9m06gYA.png" /></figure><p>Eylem olarak <strong>“Bağlantıya izin ver”</strong> seçeneğini seçip ileri dedik.Profil olarak bütün seçenekleri seçili halde ileri tuşuna bastık.(Kendimize uygun olan profili seçip ileri dedik.)Sonra bu kurala bir isim verip son butonuna tıkladık.</p><p><strong>3 .</strong> Microsoft SQL Server Management Studio da serverimize bağlandık.Security bölümünü genişlettik.Sonra <strong>Logins</strong> e sağ tıklayıp <strong>New Login</strong> seçeneğine tıklayarak SQL Server ımıza yeni kullanıcı ekleme ekranına ulaştık.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/382/1*WC5Ub7UVBnMXioihx8QUVA.png" /></figure><p>Bu kısımda Login name kısmında kullanıcı adımızı oluşturduk. <strong>Windows Authentication</strong> seçeneği yerine <strong>SQL Server Authentication</strong> seçeneğini seçtik ve güçlü bir Parola oluşturduk.Sonra ”<strong>Enforce password policie</strong>” seçimini kaldırdık. Ve pencerenin sol üst kısmında bulunan “<strong>User Mapping” </strong>bölümüne tıklıyoruz.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*OFAfixn8unRGGnTs3lZgJg.png" /></figure><p>Açılan <strong>User Mapping</strong> sayfasında kullanıcının erişmesini istediğimiz veri tabanlarını işaretleyip ve seçtiğimiz veritabanlarında sağ daki user yanındaki <strong>“default schema”</strong> kısmına kullanıcı adımızı yazdık sonra Ok a basıp devam ettik.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/684/1*j9iP0Rbl9fCnUa6uJz71wA.png" /></figure><p>Server da <strong>Databases</strong> bölümünü genşiletip kullanıcının erişmesini istediğimiz databese e sağ tılayıp <strong>properties</strong> i açtık.Burada Permissions sayfasında oluşturduğumuz kullanıcıyı seçip aşağıdaki bölümden izinleri verdik.Sonra ok butonuna tıkladık. Ve son olarak SQL Serveri restart yaptık.</p><p>** <strong>Serverimiz Hazır </strong>**</p><h3>C# ta Kurulan Local Ağdaki Server a Bağlanma</h3><p>Ayrıca c# ta bu servera bağlanmak için “<strong><em>Project &gt;Add New Data</em></strong>” Source açtık. Sonra Sırasıyla<strong> <em>Database&gt;Next-Dataset&gt;Next</em> </strong>diyoruz Ve Çıkan ekranda Server Name bölümüne Local Ağdaki IP adresimizi yazıyoruz. Authentication kısmında <strong>“ SQL Server Authentication ” </strong>seçeneğini seçip kullanıcı adımızı ve parolamızı giriyoruz. Aşağıdaki Connect to Database kısmında izin verdiğimiz veri tabanlarını görüyoruz. Ve oradan istediğimiz veritabanını seçiyoruz ve sol alttaki <strong>“test connection”</strong> butonu ile bağlantıyı test edebilirsiniz.Sonra Ok butonuna basıyoruz.Daha Sonra önceki ekrana döndüğümüzde bağlandığımız <strong>“Database”</strong> i seçip aşağıdaki kısımda Connection string…. kısmını genişletip bağlantı adresine ulaşabiliriz.Bu adresi kopyalayıp kodumuzdaki bağlantı stringi yerine yapıştırıp bu adrese kullanıcı parolasını ekliyoruz.</p><pre>SqlConnection bağlan = new SqlConnection(&quot;Data Source=localip;Initial Catalog=bilgiyarısması;User ID=kullanıcıadı; Password=kullanıcıparolası&quot;);</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7234fa246eeb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>