1

Hope everyone is doing well.

our public facing website has around 50 parts and among those 50,23 webparts are developed on

VB.net and remaining on C#.net,

Sometimes performance of the website is not getting as expecting, so Our managers have got the information from one of the sharepoint consultant that we should not use VB.net to develop webparts and we should change them all to c#.net.

My question is it neccessary? Website gets daily more than 2lakhs hits and it takes 2.seconds to 4seconds to load the complete website.

If it's neccessary to move vb.net to c#.net is there any automatic process where we can change the

VB.net code to C#.net?

Thanks in advance.

||improve this question
0

I will say it is not necessary to change web part from VB.Net to c#. Rather try to find which process is taking long time to execute, how many calls are going in that, what is the size of js, css load in that web part.

||improve this answer
  • Thank you so much for your response, May I please know is there any method to find which webpart taking how much time to complete it's process?? – Asrar Dec 20 '16 at 7:04
  • Have you write javascript code or code behind code in webpart? – Trimantra Software Solution Dec 20 '16 at 7:34
0

VB.NET as long as C# both compiled to intermediate language (called IL) code, which later gets executed by .NET runtime. Similar functions written in VB.NET and in C# produce the same IL code, that means that in terms of performance it's absolutely useless to change code from VB.NET to C#.

What you actually need is to try to find potential "bottlenecks" in web parts by using different approaches.
Let me try to list this common approaches:

||improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.