hello,i want to know why i can not start the project..Is the database disconnected?
Can we be friends? I've seen you help many people solve their problems with your enthusiasm
Thank for your answer, Now I only have the visual studio environment, and any other configuration is in the headquarters engineers.I think it is necessary for me to communicate with him
No special magic is need for using a browser. F&O is a normal web application, therefore you can either open the main F&O page and use the manu to navigate where needed, or use an address (URL) directly. The latter option is useful when the target object isn't in a menu (e.g. you're developing a form or you want to use SysClassRunner) or when you know the direct link.
I mean to say just build and sync the project without errors. Then open table browser and frontend will load. On successful load, start debugging. It should work.
How do I access it directly from the browser?
The title is wrong - your Visual Studio did start and it's running. It's clearly visible in your screenshots.
Your actual problem is with debugging. So it's not about VS, it's not about database, it's not about other service - it's about the debugger. That's why the error message says "Unable to proceed with debugging".
I must admit that I also run into problems with debugging quite often. It's important to have enough memory available; xppc.exe is what I regularly shut down to free some memory. Even with enough RAM, I sometimes get this message about timeout, but restarting VS usually does the job.
Restarting VS was mentioned above, but not the question of RAM, so check that too.
Also, if you don't need debugging at the moment, just open the web page in a browser without actually starting it from Visual Studio. VS also has an option to run a project without debugging, but it still work worse (in case of F&O) then just opening the web page.
what should i do ? build project?
Once you successfully build and sync the project then you need to refresh the frontend and once it is loaded then only start the debugger. Else it will give this error.
OK, thank You ,i will test your answer.
Try restarting the IIS.
If it doesn't work try restarting the server and check.
Also try using attach to process option.
https://dynamics365musings.com/debug-d365/
Thanks,
Girish S.
André Arnaud de Cal...
291,979
Super User 2025 Season 1
Martin Dráb
230,848
Most Valuable Professional
nmaenpaa
101,156