The requirement was to assign a click event handler to all Label Controls contained in a .NET User Control.  This is a simple technique but I found there was no good documentation on how to do this. 

To illustrate how to do this, I created a simple Windows Form application in C# and added a new Windows Forms User Control to the project.  I called it AutoLabelClickControl.  I placed a label right on the control called ‘Control Label’.  I added a panel with a label on it called ‘Panel Label’ and then placed a panel contained in the first panel and put a label on it called ‘Panel in a Panel Label’.

The idea now is that when the control ‘AutoLabelClickControl’ is loaded, code should hook up a common click event handler for all labels.  Add a _Load event handler to your Control (not the Form) using the wizard and let’s add the necessary code:

// This is the Common Event Handler for all Label Clicks
private void LabelClickEventHandler(object sender, EventArgs e)
{
    // Ensure we can typecast correctly!
    if (sender is Label)
    {
        // Do whatever you want... in this case show the Name of the control clicked
        Label aLabel = sender as Label;
        MessageBox.Show(aLabel.Name);
    }

}

// Walk the collection recursively and find Label Controls and wire them up
private void FindLabelControlsInContainerAndAssignEvent(Control.ControlCollection aCollection)
{
    foreach (Control aControl in aCollection)
    {
        // does this control contain other controls?
        if (aControl.Controls.Count > 0)
        {
            // call this function recursively!
            FindLabelControlsInContainerAndAssignEvent(aControl.Controls);
        }

        // wire up our Common Event Handler
        if (aControl is System.Windows.Forms.Label)
        {
            aControl.Click += new System.EventHandler(LabelClickEventHandler);
        }

    }
}

private void AutoLabelClickControl_Load(object sender, EventArgs e)
{
    // When loading wire up the events for all contained Labels
    FindLabelControlsInContainerAndAssignEvent(this.Controls);
}

And here is the test!

Note:  Although you may think you cannot have a label contained in a label control, you can actually do this if you edit the Designer code (not recommended) and that is why I did not have an ‘else’ statement between these:

// does this control contain other controls?
        if (aControl.Controls.Count > 0)
        {
            // call this function recursively!
            FindLabelControlsInContainerAndAssignEvent(aControl.Controls);
        }

// LOOK – NO ELSE STATEMENT… IN THEORY A LABEL COULD CONTAIN A LABEL BUT YOU WOULD HAVE TO HACK IT IN

        // wire up our Common Event Handler
        if (aControl is System.Windows.Forms.Label)
        {
            aControl.Click += new System.EventHandler(LabelClickEventHandler);
        }

It would be EXTREMELY weird for someone to do this but…  I have been around a while so that is why I wrote that code that way :-)

Note:  It is up to you to apply proper error checking and try/catch blocks to this code.  See the terms of use in my Blog header.

Please drop me a note if you find this useful!

There seems to be no simple end-to-end walkthrough for creating a simple HttpListener based SSL Listener that includes how to configure the computer by generating and installing a Certificate for this listener.

Basic concepts covered:

• Write the listener code to listen for SSL requests
• Generate a self signed Certificate
• Configure the machine to use a Certificate

Write the listener code to listen for SSL requests

Here is the documentation for HttpListener: http://msdn.microsoft.com/en-us/library/system.net.httplistener.aspx

Copy the code from the above page and paste it into a new C# Console application right under the Main() function.  Then add the System.Net namespace right under using System.Text;: using System.Net;

Now from the Main function call the function you pasted in passing the prefixes you wish to listen to.  In my case I will listen to http requests on port 8080 when the URI ends with the ‘listener’ prefix and https requests on port 8081 again with the ‘listener’ prefix.  Every time a request is handled you need to restart the program.

static void Main(string[] args)
       {
           string[] thePrefixes = { "http://+:8080/listener/", "https://+:8081/listener/" };
           SimpleListenerExample(thePrefixes);
       }

The code should now compile and you can run in the debugger.  I then used Internet Explorer to try and reach the listener: http://jsan17708317:8080/listener/ and this succeeds!  However the https site does not succeed: https://jsan17708317:8081/listener/".

The failure occurs because we have not set up a certificate for the listener to use for SSL traffic (https).  This brings us to the next two items.

Generate a self signed Certificate

First of all, if this is a production environment, you will want to get a server certificate issued by a Trusted Root authority.  This Post illustrates how to create a self signed certificate to test your code before you get a certificate from an authority.

This is the documentation for MakeCert.exe : http://msdn.microsoft.com/en-us/library/bfsktky3.aspx.  You can use this program to generate a self signed Server Certificate for the application.

Using Visual Studio 2008 you can simply use the Visual Studio 2008 command prompt from the program menu to access MakeCert.exe.

The syntax would look something like this (replace the name of the machine ‘jsan17708317’ with yours, and see the makecert documentation for an explanation of the arguments used here):

makecert.exe -sr LocalMachine -ss MY -a sha1 -n "CN=jsan17708317" -sky exchange -pe -eku 1.3.6.1.5.5.7.3.1

The command should return ‘Succeeded’.

Now you need to ensure the Root Authority is trusted.  To do this from the same command prompt you used above, type MMC.  Then choose ‘File’, ‘Add/Remove Snap-in…’

and then hit the ‘Add’ Button, select ‘Certificates’.  Click the ‘Add’ button…

Select ‘Computer account’ and then click ‘Next >’, ‘Finish’, ‘Close’ and ‘OK’.

You should them be able to expand the Tree on the left to show the Personal Certificates and find the one you just added (mine is the only one shown)…

Double click on your certificate and you will see something similar to this:

You need to resolve the Red X problem (the certificate cannot be verified up to a trusted root).

Click on the  ‘Certification Path’ tab in this dialog, and the problem certificate (Root Agency) then on ‘View Certificate’.

You will see the problem is that this Certificate is not in the ‘Trusted Root’ store. 

To get it into the store, click the ‘Details’ Tab and then the ‘Copy to File…’ button

Hit ‘Next >’ twice then the ‘Browse’ button and save the file to your local Documents directory (name it something like ‘RootCert’) then finish up the wizard until you have successfully exported the certificate.  Now we will import the certificate into the trusted root store.

Expand the ‘Trusted Root Certification Authorities’ tree and right click on ‘Certificates’

From the context menu select ‘All Tasks…’ then ‘Import…’ and navigate to where you saved the ‘RootCert’ and import the certificate by completing the Wizard.

Now you should be able to go back to your Server Certificate in the Personal Store and see that there are no problems with the Certificate (leave this dialog up for the next step):

The final step here is to get thumbprint hash for use in the next section.

Click on the ‘Details’ tab, and scroll down to the ‘Thumbprint’ Field in the dialog and click on it.  Then sweep out the numbers below with your mouse (don’t miss any) and copy those numbers with the Ctrl+C key combination.

Open notepad and paste these numbers into it for use in the next step.

Supplemental note:

If you have IIS installed, I like the SSL Diagnostics tool instead of Makecert: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=cabea1d0-5a10-41bc-83d4-06c814265282 Instructions for generating the certificate are in the help file for this tool.  Once you run this tool it creates a temporary certificate and installs it in the local computer Trusted Root Authorities Certificate store for you!

Configure the machine to use a Certificate

Finally you need to configure the machine to associate the certificate you just created, with the port and ip address that the HttpListener is listening on for https requests.

You need to obtain httpcfg.exe to do this next step.  Search Technet for the latest version of this tool for your OS.  For example, XP SP2 tools have it (Note: this is an optional component for XP so you will need to do a COMPLETE install to get this tool): http://www.microsoft.com/downloads/details.aspx?FamilyId=49AE8576-9BB9-4126-9761-BA8011FABF38&displaylang=en

You will need to run httpcfg from the command line and supply the Thumbprint hash you obtained in the previous section but you need to remove the spaces between the numbers.  In my example I removed the spaces and the hash is: f4bb35424190e006e5476e97430c5b8136ee5da5

This is the httpcfg command I ran to associate the cert for all IP addresses associated with my machine and port 8081 (/i 0.0.0.0:8081):

C:\Program Files\Support Tools>httpcfg set ssl /i 0.0.0.0:8081 /h f4bb35424190e006e5476e97430c5b8136ee5da5

When you run this you will see the result: HttpSetServiceConfiguration completed with 0.

Now double check the SSL bindings for this computer:

C:\Program Files\Support Tools>httpcfg query ssl
    IP                      : 0.0.0.0:8081
    Hash                    : f4bb35424190e0 6e5476e9743 c5b8136ee5da5
    Guid                    : {00000000-0000-0000-0000-000000000000}
    CertStoreName           : (null)
    CertCheckMode           : 0
    RevocationFreshnessTime : 0
    UrlRetrievalTimeout     : 0
    SslCtlIdentifier        : (null)
    SslCtlStoreName         : (null)
    Flags                   : 0
------------------------------------------------------------------------------

Now you should be able to run the above Test application and hit the SSL Site using Internet Explorer.  In my case the URL is: https://jsan17708317:8081/listener/

Troubleshooting

If the app does not work, first verified you did each step above correctly (did not leave out something or some step).

Verify your certificate appears with the IP and Hash fields the correspond with what you are listening for and that the Hash is the hash you obtained previously for the certificate.

Check with httpcfg query ssl and see if there are other listeners that may conflict for that same port.  Delete conflicts with the command http delete ssl /i x.x.x.x:8081  (replace x.x.x.x with any IP address you see that are listening on the same port).

Supplemental Information

This is a simple example.  You probably do not want to stop listening after you process one request.  You will need to provide a way to gracefully close the listener and handle the requests on worker threads.

You can specify a specific IP range in HttpCfg (search MSDN for HttpCfg syntax).  In my example you can use this to bind to the ip address 10.10.3.4:
httpcfg set ssl /i 10.10.3.4:8081 /h f4bb35424190e006e5476e97430c5b8136ee5da5

You cannot listen for http and https traffic on the same port.

I hope this gets you started with your HttpListener project and will help you troubleshoot the initial setup of your code.  Please Drop me a note if you find this useful!

This error message is caused because the process is not being able to validate the Server Certificate supplied by the Server during an HTTPS (SSL) request.  The very first troubleshooting step should be to see if the server supplied certificate and every certificate in the chain is trouble free.

Example 1 – Root Certificate only (self signed certificate in this case)

Step 1 – Validate the certificate, any intermediate certificates and the root certificate

One super handy and technical tool to help you do this first step is Internet Explorer.  Simply try to hit the same URL that your ASP.NET web application tries to hit when it gets this error.  For example, type in to the browser the path to the .asmx file and see what Internet Explorer says about the certificate.

This would be a bad sign:

If Internet Explorer has certificate problems, chances are you will have problems with the HttpWebRequest (or Web Service) call as well.  The easiest fix is to install a valid certificate for the server, the root authority and all intermediate authorities.  Then go back and verify Internet Explorer can access the https site with no errors at all.

If you continue to the site using Internet Explorer, sometimes you can diagnose the certificate problem by viewing the certificate.  In this example the problem is spelled out for me when I typed in https://jsanders4.

So in my case, it appears that the I simply need to install the certificate in the ‘Trusted Root Certification Authorities’ store.  So indeed I do this!

But I still got the certificate error…  To avoid a long discussion about this, the problem is simple.  I typed in https://jsanders4 but note the certificate is for the full domain name of this machine.  If I instead browse to https://jsanders4.northamerica.corp.microsoft.com then I get no certificate error.  Now that I am sure I can browse ok to the site with no certificate errors using Internet Explorer.

You would continue to solve problems with the other Certificates in the Certificate chain by using Internet Explorer until they are all resolved.  For example, perhaps the certificate is expired, or the Intermediate Authority is not in the Intermediate Certificate Authorities store (a very common one).  Once you have resolved all errors with Internet Explorer your are only half way finished.  You need to get the same information into the Local Computer store.

Step 2 – Troubleshoot the ASP.NET problem

I try my ASP.NET application and try to access the same site.  I get this error: ‘The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.’

But Internet Explorer was fine…

The next step should be to get a System.Net trace.  To do this open the Web.Config for the troubled ASP.NET application and see if there is a <configuration> section in the file.  If there is, add the contents inside the <configuration> </configuration> tags from this blog: http://blogs.msdn.com/jpsanders/archive/2009/03/24/my-favorite-system-net-trace-configuration-file-dumps-process-id-and-date-time-information.aspx.  If it does not exist, add the entire contents before the closing tag of the Web.Config.  Now edit this line:   initializeData="System.Net.trace.log"  You must ensure that the Network Service account can write this .log so change this entry to a folder that the Network Service account can write to.  For example, I created a folder c:\mylogs and assigned the Network Service account FULL privileges.  Then changed this setting to initializeData="c:\mylogs\System.Net.trace.log"

I ran the asp.net application and saw at the end of the log file (c:\mylogs\System.Net.trace.log) this information:

System.Net Information: 0 : [0880] SecureChannel#14701405 - Remote certificate has errors:
    ProcessId=5700
    DateTime=2009-09-16T12:54:06.5718699Z
System.Net Information: 0 : [0880] SecureChannel#14701405 -     A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.

    ProcessId=5700
    DateTime=2009-09-16T12:54:06.5718699Z
System.Net Information: 0 : [0880] SecureChannel#14701405 - Remote certificate was verified as invalid by the user.
    ProcessId=5700
    DateTime=2009-09-16T12:54:06.5718699Z
System.Net.Sockets Verbose: 0 : [0880] Socket#26833123::Dispose()
    ProcessId=5700
    DateTime=2009-09-16T12:54:06.5718699Z
System.Net Error: 0 : [0880] Exception in the HttpWebRequest#31364015:: - The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
    ProcessId=5700
    DateTime=2009-09-16T12:54:06.5718699Z

This is the key to this particular problem:  A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.

However I thought I just added this certificate trough Internet Explore to my Trusted Root Authorities!  In reality I simply added it so the store of the logged on user.  ASP.NET is running in the local machine context.  To resolve this, start MMC (Windows key + R and type MMC) and add the following snap-ins:

And ensure you see the ‘Current User’ and ‘(Local Computer)’ Certificates listed (then hit OK):

In the console expand the ‘Current User’ Trusted Root store and you see I have the certificate stored there.  However expanding the ‘(Local Computer)’ trusted root, it is NOT there:

Simply Copy (do not Drag and drop) the jsanders4 certificate from the Current User\Trusted Root store to the (Local Computer)\Trusted Root store and retest. 

Success!

Example 2 – Intermediate Certificate Authorities Involved

This next example is a bit manufactured but illustrates a problem that I have had to help solve a few times.  The trouble shooting steps remain the same, but in this case there are one or more intermediate certificates.  This intermediate certificates should be in the ‘Intermediate Certification Authorities’ store to resolve this problem Take a look at the certificate chain for https://www.microsoft.com (you do this by clicking on the padlock icon in Internet Explorer and choosing the Certification Path tab:

For the purpose of this example, assume that the three certificates that are not highlighted all have a warning icon next to them indicating a problem.

Step 1 – Validate the certificate, any intermediate certificates and the root certificate

Note: For Internet Explorer there actually was no problem with the certification path.  The four certificates show no warning icons.  For this example, let’s say that the ‘GTE CyberTrust Global Root’, ‘Microsoft Internet Authority’ and ‘Microsoft Secure Server Authority’ certificates were all missing from my ‘Current User’ stores.  The steps below are contrived from this assumption.

To fix this I add the ‘GTE CyberTrust Global Root’ cert to the ‘Trusted Root Certification Authorities’ Store and the other two certificates to the ‘Intermediate Certification Authorities’ store of the Current User.  Test with IE again and Internet Explorer shows no problem after installing the certificates.  Next when I tested the ASP.NET application I got an error (because I did not add these certificates to the same stores in the (Local Computer) store).

Step 2 – Troubleshoot the ASP.NET problem

From the first example I was smart enough to copy the ‘GTE CyberTrust Global Root’ certificate to the ‘(Local Computer)’ trusted root store but I still have an error!

The ASP.NET program now has an error: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.

Again taking the System.Net trace you see an error towards the end of the file in these entries:

Remote certificate has errors:
A certificate chain could not be built to a trusted root authority.
Remote certificate was verified as invalid by the user.
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.

This entry is the key: ‘A certificate chain could not be built to a trusted root authority.’  This means that a certificate before the Root Authority is not in the ‘(Local Computer) Intermediate Certification Authorities’ store.  Once the two intermediate certificates are copied to the Intermediate store from the Current User intermediate store the problem is solved!

I hope this blog helped you get to the root of your problem.  If this was helpful please leave me a comment!

A little know fact is that the .NET framework will use the stored credentials in the Credential Manager when accessing a network resource if the credentials exist for that particular resource (host).  I intend to clear up how this functionality works for the HttpWebRequests (you could extend this to WebService calls as well).

In Internet Explorer, you can access a website that challenges you for credentials by filling in a username and password when the dialog is presented and asks you for authentication.  If you check ‘Remember my password’ these credentials will be stored in protected storage (Credential Manager).  You can see the stored credentials by running this command: Control Keymgr.dll.  These credentials are stored in protected storage in each user’s My folder.  You can store these credentials by using control Keymgr.dll, by using the interface available in Internet Explorer or by using C++/C and the Credentials API’s (Such as CredWrite).  If you do not check ‘Remember my password’ then these credentials are not stored in Credential Manager and .NET will not be able to use these credentials.

The .NET framework can use the currently logged on user’s credentials to authenticate but if you have a web site that requires different credentials you can use store these credentials in Credential Manager and .NET will use these credentials instead of the currently logged on user credentials.  To illustrate this I put together a real simple sample.

The target web server in my sample is jpsandershv2003.  I only enabled Windows Integrated Authentication in IIS on that box.  I then created a User ID JPSGuest on that IIS machine.  Finally I wrote a real simple .NET console application to create an HttpWebRequest and get the response.

   HttpWebRequest aReq;

   HttpWebResponse aResp;

   aReq = WebRequest.Create("http://jpsandershv2003/") as HttpWebRequest;

   aReq.UseDefaultCredentials = true;

   aResp = aReq.GetResponse() as HttpWebResponse;

   aResp.Close();

When you run this code it will first look in the credential manager first for the credentials for attaching to jpsandershv2003 and if found use those, otherwise the Currently Logged on User credentials will be used.  In my example since I was logged on as jpsanders to my machine I expect that the credentials used should be my domain credentials jpsanders.  I turned on logging and ensured the IIS log was logging the username and sure enough, jpsanders was authenticated in IIS.

My next goal was to see if I could change this default behavior and make it log on using the jpsandershv2003\JPSGuest user credentials.  Using the command control keymgr.dll I was able to add the credential as a Windows logon credential:

Now when I ran the console application I saw success in the IIS log!  I was logging in now as JPSGuest.

Taking a fiddler (http://fiddlertool.com) trace of Internet Explorer also confirmed I was using the stored credentials and these were NTLM credentials. 

Domain: jpsandershv2003
User: JPSGuest
Host: JPSANDERS3

Can I store credentials and have it use Kerberos?  In theory yes, simply type domain based credentials in.  However I could not test this because I only have one logon to my domain and you cannot save your currently logged on credentials in the Credential Manager. 

What about basic and digest?  NO, this would be a huge security hole.  Can you tell me why (it should be obvious)?

Note that the credentials used are independent of the PORT used.  So if I change the server to bind HTTP traffic on port 8089 then change my code to access http://jpsandershv2003:8089 the code will still access the web site using the stored credentials.

To revert back to the interactive user, simply delete the credentials stored for jpsandershv2003.

Further observations

What is the second radio button for (A Web site or program credentials)?  This is for programs that are writing against the credentials API directly.  Some examples of this are Terminal Server (RDP) and Windows Live credentials.  Here are some great links about the APIs:
http://msdn.microsoft.com/en-us/library/aa374789(VS.85).aspx
http://msdn.microsoft.com/en-us/library/aa480470.aspx

NOTE: Because the credentials are stored in the context of the logged on user, this technique will not work for non interactive user accounts such as the service accounts and ASP.NET applications.

Please send me a quick note if you found this Blog helpful!

David Wang wrote an excellent post about this in 2006:  http://blogs.msdn.com/david.wang/archive/2006/02/09/Can-I-write-an-ISAPI-Filter-using-Managed-Code.aspx

This includes writing ISAPI code that even USES managed components.  Anything that needs to load the CLR will result in poor performance of the ISAPI and worse, result in ASP.NET not functioning correctly.

ASP.NET loads the CLR when it initializes.  During this loading it does many things to configure the CLR.  One example is that it creates on GC thread for each processor on the system.  It also sets up some defaults for the thread pools.  When you write your ISAPI in managed code or include a COM Visible .NET component through COM in your code, your ISAPI loads the CLR.  Since only one CLR can be loaded per process, ASP.NET will not create and configure the CLR and you are left with a severely crippled system.

This problem can also occur if you write an ISAPI Extension.  Your Extension could load the CLR runtime if you hit a static file first, initialize the CLR in the ISAPI Extension by using .NET or a COM Visible .NET object and then hit your ASP.NET application after this initialization.

You can clearly see this in a multi processor machine if you create a filter that uses a Managed code COM component.  Without your filter in place, hit an aspx page on the site and use DebugDiag to take a dump of the w3wp.exe process.  Then analyze this dump with DebugDiag.  You will see a GC thread initialized for each processor core installed on your server.  On my server I have a quad proc CPU and I see 4 threads with this in the call stack: mscorwks!SVR::gc_heap::gc_thread_function.

Then I created a simple ISAPI filter from one of the existing Platform SDK samples and simply instantiated a COM Visible .NET component.  I installed the ISAPI filter and re-ran my test.  As expected, I saw only 1 thread with mscorwks!SVR::gc_heap::gc_thread_function.

This problem manifests itself not only with the GC threads but all the information set by the processModel (see http://msdn.microsoft.com/en-us/library/7w2sway1.aspx).  In theory you could come up with some sort of scheme to read the machine.config file and parse and set this information, but this is untested and definitely not supported (read: you are on your own).

If you really are in need of writing Managed Code, you should investigate the Managed Pipeline in IIS 7 and use that http://msdn.microsoft.com/en-us/library/ms227673.aspx.  There are a couple of other workarounds you could explore like out of proc components etc... but these would all create performance issues for a Filter or Extension.

Please let me know if this blog post was useful to you!

I came across this problem.  The key to this was that the documents opened fine when clicking on them, so I knew the Office installation itself was fine.  Some rogue application on install or removal had apparently removed the appropriate Content Type registry key so Internet Explorer was unable to associate the XML file extension with any application.  Restoring the default OS registry entry allowed everything to start functioning again.  Warning, modify the registry at your own risk.  Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\.xml]
"Content Type"="text/xml"

Why did this rogue deletion of this registry key affect IE but not the InfoPath application itself?

Since all the registry entries for the application were correct the associations in the registry for opening the file are in place.  The issue is that with the 'Content Type' entry missing, Internet Explorer (more precisely Urlmon used by IE) is unable to determine what to do with this particular Content Type (XML). When this key is correct, this MIME type is found in the MIME Database registry location and the appropriate application can be invoked.

Since Office is installed the file will be passed to MSOXMLED.EXE which will determine the correct application to invoke by looking inside the XML for the appropriate entry indicating what application that particular XML is associated with.  For example: <?mso-application progid="Word.Document"?> indicates that this is a Word Document.

Let me know if this blog helped you by dropping me a note! 

I like to build and run with UAC on.  When running the HttpCalculatorService example I got this error: 

 Failure: errorCode=0x80070005
Unable to add URL to HTTP URL group.
Access is denied.

Running from an administrator command prompt I do not get the error!

Obviously I do not have permissions to something.  Some investigation revealed that I need to add the user I wanted to run as to the urlacl (http://msdn.microsoft.com/en-us/library/cc307223(vs.85).aspx)

So this is the command that allowd me to run (replace myDOMAIN\myUSERNAME with the domain and user you wish to run the Service under): netsh http add urlacl url=http://+:80/example user=myDOMAIN\myUSERNAME.

To do this in code you could use this API: http://msdn.microsoft.com/en-us/library/aa364503(VS.85).aspx but the code your are running would need to have the necessary permissions so you are in kind of a chicken and the egg situation!

Drop me a comment and let me know if this helped you please!