How can we help you today? How can we help you today?
ashars

Activity overview

Latest activity by ashars

Hey skaithi, I've encountered the TF30063 error before, and it can be quite frustrating, but fear not, I've got a solution that might help you out. First off, it's crucial to ensure that your Visual Studio is running with the right permissions and identity. It appears that your configuration and connection details are mismatched. Here's what you can do: 1. Registry Cleanup: As you've rightly pointed out, sometimes remnants of old credentials can lurk in the Windows Registry. Navigate to "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VSCommon\Licenses\17.0\VisualStudio" and remove any entries related to SKaithi or the problematic identity. This should help in refreshing your credentials. 2. Switch User Operation: Follow the error's advice and perform a "Switch user operation" within Visual Studio. It might prompt you to re-enter the correct credentials, which should establish the right connection. 3. Verify Configuration: Double-check your project settings and make sure they align with your source control provider settings. Any mismatch here can trigger such errors. 4. Update Visual Studio: Ensure you have the latest updates for Visual Studio, as newer versions often come with bug fixes and improvements related to authentication. I hope this helps you resolve the issue and get back to linking databases to source control smoothly.  / comments
Hey skaithi,I've encountered the TF30063 error before, and it can be quite frustrating, but fear not, I've got a solution that might help you out. First off, it's crucial to ensure that your Visual...
0 votes
Hey arrelligu, I feel your frustration with profiling ASP.NET Core 2.1 applications. Profiling can indeed be a tricky endeavor, but fear not, I'm here to shed some light on the matter. Firstly, ensure that you're using a reliable profiler tool. For ASP.NET Core 2.1, I recommend leveraging the power of Visual Studio Profiler, which can provide in-depth insights into your application's performance. Additionally, if you're looking for specialized expertise and support in optimizing your ASP.NET Core applications, you might want to consider consulting with companies like Andersen, known for their expertise in software development and performance optimization. Now, onto your configuration. The snippet you've shared seems alright. However, it's essential to make sure you're targeting the right process. As you rightly mentioned, it captures data for the web host, but often, you need to dig deeper. In your profiler tool, check the thread dropdown. Sometimes, there are multiple dotnet.exe threads running, each corresponding to different aspects of your application. Try selecting a different thread to capture more comprehensive data. In my experience, adjusting thread selection often does the trick. Give it a go, and you might unveil the profiling treasure trove you seek. / comments
Hey arrelligu,I feel your frustration with profiling ASP.NET Core 2.1 applications. Profiling can indeed be a tricky endeavor, but fear not, I'm here to shed some light on the matter.Firstly, ensur...
0 votes