Microsoft Dynamics 365 – Page 194 – Nishant Rana's Weblog

Empty or Disable cache while working with Web resources in Dynamics 365 (Chrome)

Most of the time while developing Web Resource we need to frequently update and publish it. We need to make sure that it is not cached and our changes are reflected instantly on publish.

For Chrome,

Open the Developer Tools (F12)

Press and hold the reload button and select “Empty Cache and Hard Reload” to have changes reflected.

https://stackoverflow.com/questions/14969315/whats-the-difference-between-normal-reload-hard-reload-and-empty-cache-a/14969509#14969509

The other option à Developer tools – Settings – Preferences

Hope it helps..

How to – Update Schedule of existing Azure WebJobs (triggered)

Suppose we have following WebJob deployed in Azure of type Triggered.

And now we want to update its schedule.

To do so,

Open the App Service Editor

Update the CRON expression in settings.job (in case of scheduled web job), if the file is not there we can create and add it.

This makes the Webjob to run every 1 minute.

Back in our Webjob we can see the schedule updated.

Inside the logs à

More details –

https://github.com/projectkudu/kudu/wiki/WebJobs#scheduling-a-triggered-webjob

Hope it helps…

Using log4net with Azure WebJobs

To get started, let us create a C# Console Application and add the NuGet Package for log4net.

Update the App.Config with log4net configuration.

The most important part here is value of file.

The D:\Home\LogFiles is the path where our WebJob can write to.

https://docs.microsoft.com/en-us/azure/app-service/web-sites-enable-diagnostic-log#download

Inside our program.cs initialize the log4net.

Publish the WebJob to Azure.

Open the Kudo, we can see the Folder created

And our log file

Get all the details here

https://blogs.msdn.microsoft.com/benjaminperkins/2017/09/27/how-to-configure-log4net-on-azure-app-service/

Hope it helps..

Capturing Dynamics 365 client side performance telemetry with Azure Application Insights

via Capturing Dynamics 365 client side performance telemetry with Azure Application Insights by Dilip Kumar

Fixed – Wi-Fi Network not showing up in Windows 10

[Update – 6th June 2018]

Finally working now –

Tried starting all the network and update related services randomly in Windows Services (Run –> Services.msc).

2018-06-06_0720

Here are the list of services running in my machine

Try starting them and see if it works for you .

https://drive.google.com/file/d/1GD1HG4S5goMod8u4GgbcvORIeC7Z3VXi/view?usp=sharing

[Update – 2nd June 2018 – Still can’t see the wifi network, have tried all the option. I think will have to format it. Meanwhile using the below approach]

Few days back I saw that my Lenovo (Windows 10 ) laptop was not showing any WIFI networks.

I tried everything that was suggested out there i.e. update drivers, configuring WLAN Auto Config, Auto Discovery On etc. etc. (except the last resort of formatting the operating system) but none worked.

Interestingly it was showing all the available networks on the lock screen, through which I was finally able to connect.

The other option that could help is, from the command prompt delete the existing profile using the below command

netsh wlan delete profile name=”WifiName”

and create a new wifi connection manually and start it automatically.

I think some of the Windows updates might be the reason for this issue, so still waiting for a newer update that might fix it. Till then at least I have the above workaround.

Hope it helps.

Using Azure Hybrid Connections to connect to SQL On-Prem Database from Azure WebJob.

Updated = 23rd September 2018.

Hybrid Connections allows Azure Web Sites and Services to securely connect to the on-premises resources hosted within the corporate network, without requiring any change to firewall or network.

Hybrid

Prerequisites: –

Azure Subscription
TCP/IP protocol needs to be enabled.
SQL Authentication (1433 Default Port for Default Instance)
Windows Server 2008 or later and outbound internet connection and can talk with LOB application – SQL Database.

Multiple Hybrid Connection Manager can be installed in separate server that can do the load balancing.
Hybrid connection implements Transport Layer Security between the cloud and the on-premise endpoint for data encryption.
Hybrid Connection Uses Shared Access Signature for securing the End Points.

Here we’d take a simple example of creating an Azure WebJob that will connect to the SQL On-Prem Database.

To start with, create a console application that connects to SQL On-Prem Database and pulls information from a table inside it.

Publish it as Azure WebJob.

Click on Publish to publish the WebJob.

Back in Azure Portal, we’d see our WebJob. Click on Run to start the WebJob. And click on Logs.

As expected we’d get the SQL Exception as Web Job will not be able to connect to the On-Prem Database.

Now let us configure Hybrid Connection to get the WebJob up and running properly. Inside the App Service select Networking and click on Configure your hybrid connection endpoints.

Click on Add hybrid Connection.

Here Endpoint Host will be the name of our OnPrem Machine\Server, Endpoint Port will be the Port for the SQL Server (1433 for the default instance).

Next step is to install and configure Hybrid Connection Manager.

Once installed, open the Hybrid connection manager and click on Add a new Hybrid Connection

If everything is correct, it should show the status as connected.

*I had to restart the Azure Hybrid Connection Manager Service after adding the connection for the Azure status to show as connected

Now back in our WebJob, let us click on Run.

In logs,

we’d see the data successful fetched from our SQL On-Prem DB.

In case of named instance of SQL, we need to create a new hybrid connection with the specific TCP Port used by that named instance.

To find the port used by the named instance, open SQL Server Configuration Manager, select the named instance of SQL and copy the value of TCP Dynamic Ports.