Juan Liner

Here's a well-written update to a long-standing resource on #reactiveprogramming in #dotnet - where it all began. It's a #freePDF and available online. Intro to Rx -- https://introtorx.com #softwareengineering #webdevelopment #iot #cloudnative #cloudcomputing

1

Fair day of trying to upgrade our CMCI and WUI to the new JVM that CICS 5.6 uses. Couple steps of what needed to be done when our WUI would not communicate with the default properties for javaserver= True in the toggle configuration. 1) configure an Angel process for effective security and communication - tried disabling “halt liberty server with no angel process to = false” but cics did not like that :) 2) created RACF definitions to configure a new angel process STC. 3) created the RACF necessities for bbqzangl to work and communicate with the CICS userID and also uncommented Dcom.ibm.ws.zos.core.angelName=named_angel and inputted our ANGEL process name for best practice. This is inside the EYUCMCIJ.JVMPROFILE in the Java profile directory found inside the CICS root - I found this article to help with RACF requirements for enabling a new angel process https://lnkd.in/g9vAbvJB 4) create some JCL for the started task and put the ROOT directory location of your Java native files (inside the WLP directory. - If you run z/OSMF, there is a started task named IZUANGx that will help with how the STC should be look. 5) if all your requirements are met you should be able to start your new angel process. - I ran into an issue originally with an error code of 00009D. This ended up being an issue with the native file extended attributes settings (Apf and program control were all set to No) inside the Java native directory. The file path is usually listed above the error. I had to refer to the zosconnect angel process native files to see the correct attributes needed. 6) once that the STC is running you should be able to start the region that has the WUI and look out for messages that state “the WUI was connected to JVM server successfully” (atleast something in that realm of wording) 7) usually if it doesn’t connect successfully you will see why. For me, it was the RACF definitions under the SERVER class not having access to CICS. You would have to make sure that the profile that was created under the server class for the new ANGEL process and the CICS USERID has access to the profile. Anyways, trying to remember that from the top of my head may have been confusing but that’s what it is :) #CICSprogrammer #zos #cicsts5.6 #IBMchampion

5

In case you missed our collaborative Feature Spotlight with Ministry of Testing, check out the link below to watch it!

6

🚀 Thinking about migrating your legacy systems to .NET? Let's dive into why this might be the game-changer you've been waiting for! 🖥️💡 🌟 Performance Boost .NET offers a significant performance improvement over many older systems. Faster operations mean happier users and more efficient processes. Who doesn't love speed? 🏃‍♂️💨 🔒 Enhanced Security With .NET, you get top-notch security features. Protect your data and give your clients peace of mind. After all, safety first! 🛡️🔐 🔧 Maintenance Made Easy Say goodbye to cumbersome updates and hello to seamless maintenance. .NET's robust framework simplifies the process, saving time and reducing headaches. 🧰✨ 🌐 Scalability at Its Best Planning to grow? .NET scales with you. Whether you're expanding your user base or adding new features, .NET has got you covered. 📈🚀 🤝 Strong Community Support Join a vibrant community of developers who are ready to help and share their knowledge. Collaboration has never been easier! 🤗👥 Ready to make the leap? Share your thoughts below! Have you already migrated to .NET or considering it? Let's chat! 💬👇 https://lnkd.in/gJu_fKhF Book a live demo meeting: https://lnkd.in/dNZWEutE #LegacySystems #DotNet #TechUpgrade #Innovation #Productivity #Security #Scalability #CommunitySupport #techcronus #dotnet #system #hiredotnetdeveloper #developmentcompany

4

If you're looking for an #fsharp library that lets you easily build up indented text (for example, F# or YAML), check out StringBuffer by Simon Reynolds! #dotnet

1

Setting Up and Writing Unit Tests in .NET Core Master the essentials of unit testing in .NET Core! Learn to set up and write effective unit tests to ensure your code is robust, reliable, and bug-free.

6

1 Comment

Sometimes, the rules let us cheese the dice rolls. This morning’s video goes through adding more tests for our assumptions about how that behavior should work, and then I start implementing. Link’s in the comments. #thatDeveloperDad #liveCoding #testFirst #cSharp #dotNet 

1

1 Comment

📣 A new article is out! 📣 This time I decided to write an article that yes, mainly targets #dotnet developers (in particular, those not used to working with NPM and Git Hooks), but it is also useful for developers working with other languages. 𝑯𝒐𝒘 𝒕𝒐 𝒄𝒖𝒔𝒕𝒐𝒎𝒊𝒛𝒆 𝑪𝒐𝒏𝒗𝒆𝒏𝒕𝒊𝒐𝒏𝒂𝒍 𝑪𝒐𝒎𝒎𝒊𝒕𝒔 𝒊𝒏 𝒂 .𝑵𝑬𝑻 𝒂𝒑𝒑𝒍𝒊𝒄𝒂𝒕𝒊𝒐𝒏 𝒖𝒔𝒊𝒏𝒈 𝑮𝒊𝒕𝑯𝒐𝒐𝒌𝒔 For sure, having standardized commit messages can bring so many advantages to the table. Do you have them set in your projects? https://lnkd.in/dHWrKjjR #git #teamculture #pullrequests

7

This is a great improvement to see in #Laravel. Helps reduce the amount of code needed. https://lnkd.in/gK_xWJHC

1

Are you developing a .NET application with C# and need to send custom emails? Look no further! One of the best parts of .NET is the abundance of (often free) libraries available via NuGet. My go-to for sending emails is MailKit, provided under the MIT License. To get started, you’ll need an SMTP server, which is typically part of cloud subscriptions like Microsoft, Google, or Amazon, and an application built using C# in Visual Studio. Import MailKit via NuGet (version 4.6.0 used here) and ensure you have a server for hosting your application—often M-Files in our case. Remember to securely store SMTP connection details and make them easy to update. In M-Files, this means configuring and masking the password field. Learn more about sending emails using C# here: https://bit.ly/4cLSqC8 #CSharp #DotNet #MailKit #EmailAutomation #EmailDevelopment #NuGetPackages #SMTP #MFiles #SoftwareDevelopment #CodingTips #DevCommunity #Programming #TechTips #CloudComputing #VisualStudio #SoftwareEngineering #TEAMIM

5

Interviewed a senior .NET developer candidate today - mixed bag🛍️. Technically solid with the basics👍, but lacked functional understanding🧠. When given a real-world problem, he couldn't visualize how it would translate into application flows and functionality📲. I get that coding is one skill👨‍💻, but being able to connect the technical dots to the functional picture is huge🌐. I need developers who can not just write code, but understand why they're building something and how it impacts the business📈. This guy might be a coding whiz🚀, but without that functional mindset and problem-solving ability, he's just a code monkey🐒. He's got potential, but to really level up, he needs to start thinking beyond just the tech and add more strategic value💡. At the end of the day, I want developers who can be true assets to the organization, not just order-takers📝. A little more functional prowess from this candidate would've gone a long way🛣️.

20

Warning: this is a long boring ASP.net Core developer story if you don't want to read just go to Conclusion. Well Last Night I just Decided to Add Lazy loading to an ASP.net core web API project. ( I've never did it before ) so I went on and added the official crucial package to the project ( the Microsoft Entity Framework core Proxies ). Here after doing some necessary changes I compiled the project and run it. when my App crashed and I got the error "Method GetQueryProvider bla bla bla does not have any implementation" everything changed and the plan went to search the error instead of implement Lazy Loading 😩 . So after some searching I found out my proxies package version is 7.0.8 and SQL package is 6 and I need to update it. here I Decided to Update all EntityFrameWorkCore Packages, every one updated except the Authentication.JWTBearer package and it keeps giving me that the target netCore version must be +7 and it was at that time that I realized "JUST downloading and installing netCore v7 wont change your target version for your current app: ( which actually makes sense 😓 ). After Changing the target version I thought to my self that it gonna be it and it will run now ( poor naive me ). the Next error literally was "a connection was successfully established with the server, but then an error occurred during the login process bla bla bla and The certificate chain was issued by an authority that is not trusted." which literally likes "I just don't want to run and irritating you is fun" Well, now again after searching I found out that some encrypt option is now by default went to true and I need to add "TrustServerCertificate=True" in my connection string ( which is off course NOT Recommended and you need to provide a certificate for your server ) but who gives a thing when you just want to add Lazy Loading for first time to your project ( and now you don't even remember what were you doing in the first place ). But Here I am After all these changes and searching the App ran successfully 🤘 . how ever now I didn't remember what was I doing in the first place 👀 . conclusion: developing an App needs patience( LOTS OF patience ). This is our Job. this is what we developers do and every time you go through it you learn something ( and forget what were you doing ). and to be honest this was just a very small reminder cause I'm sure all you developers been through much worse than it. like me and my friend Farshad Gholami Experienced much bigger problems like this when we where developing game together.

1

New blog alert! 🚨💻 Discover the ultimate comparison between .NET Core and .NET Framework. 🔍 Explore the all-inclusive comparison guide to understand their key differences and benefits. Find out which is best for your next project. #DotNetDevelopment #DotNetCore #DotNetFramework #DotNetDevelopmentCompany #DotNetDevelopmentServices #CEO #CTO https://lnkd.in/d8cZWiX4

15

1 Comment

Understanding Big O is essential for choosing the right algorithm to solve a problem

4

1 Comment

This article shows how an ASP.NET Core application can access an ASP.NET Core API using OAuth Demonstrating Proof-of-Possession (DPoP). This is a really powerful security enhancement which is relatively easy to support. The access tokens should only be used for what the access tokens are intended for. OAuth DPoP helps force this. This solution was created using Duende IdentityServer and the Duende samples. The OAuth 2.0 Demonstrating Proof-of-Possession at the Application Layer (DPoP) is still a draft standard. #aspnetcore #dotnetcore #identityandaccessmanagement #security #authentication #authorization #oauth2

4

🚀 Exciting news for .NET developers! 🚀 In the latest edition of C# Insights, we featured a fantastic blog post by Nick Cosentino titled "MudBlazor With Blazor Interactive SSR – What You Need To Know". If you're diving into Blazor development or looking to enhance your skills, this guide is a must-read! Here's a sneak peek of what you'll find in the article: - Understanding MudBlazor: A Material Design component framework for Blazor, designed for rapid web application development without the hassle of CSS and JavaScript. - Exploring Blazor Render Modes: Learn about the different render modes and why Nick chose the Interactive Server mode for this setup. - Step-by-Step Setup Guide: Follow along as Nick walks you through setting up a new Blazor project, configuring MudBlazor, and utilizing its components effectively. Whether you're building a simple application or a complex web solution, understanding how to leverage MudBlazor with Blazor interactive SSR can greatly enhance your development process and user experience. Ready to dive in? Check out the full blog post here: https://bit.ly/3QCpeVs 📌And don't forget to subscribe to C# Insights for more curated content and valuable resources for .NET developers! #CSharp #DotNet #Blazor #MudBlazor #SSR #WebDevelopment #SoftwareEngineering #CSharpInsights

2

1 Comment

🌟 Exploring .NET FAQs: Your Guide to Mastering Development! 🌟 Curious about .NET development? Join us as we explore the exciting world of .NET and uncover answers to your most pressing questions! 💡💻 Q: Why should I use C# for .NET development? A: C# is like your versatile coding buddy. It combines simplicity, strength, and scalability effortlessly, much like a trusty Swiss army knife for coding. Whether you're crafting quick solutions or complex systems, C# ensures tidy, bug-free code with its strong typing. And with seamless integration into the extensive .NET ecosystem, turning your ideas into reality is swift and straightforward. #DotNET #SoftwareDevelopment #FAQs #ArwaTechnologies

4