TOPIC:

Tomorrow is the official launch of Visual Studio 2019. Unfortunately Microsoft has changed some things in Visual Studio, especially the "New Project" dialog which make it difficult to use VS 2019 with X#. Our project templates are almost invisible in this new dialog....

The X# installer does recognize VS 2019 and installs in this version, and you can also open, edit, compile and debug fine in VS 2019, but creating new projects has become complicated because our templates are treated differently then the built in templates for C#, VB and other Ms languages. And we are not the only ones suffering from this. Almost all 3rd parties have complained about this.
We were promised that they'll make some changes in Update 1 (most likely released in May or June 2019) that will make us properly visible again on this New Project dialog.
So I would recommend everybody to keep on using VS 2015 or VS 2017 until this has been fixed.

You can help to tell Microsoft that they need to fix this urgently by leaving a comment on this page:

developercommunity.visualstudio.com/idea...10214#comment-510214

Robert

Hi Robert,
thank you for confirming this. I have added a comment now on this page.
Wolfgang

If you type "xsharp" into the Search box on the new project dialog, you can find the 8 template X# projects that way. Not a big deal I would reckon because anyone who's gone to the effort of installing X# will know to look for X# projects if that's what they want to create. Obviously, it would be better to appear in the Language dropdown.

p.s. Searching "X#" only returns 3 results. It might be worth updating the integration to get all the results to return as per "xsharp".

fxm wrote: p.s. Searching "X#" only returns 3 results. It might be worth updating the integration to get all the results to return as per "xsharp".

IIRC, the reason for this is in MS, Robert commented about it some time ago...

On #1:
Done:

---

Indeed!

Why does Microsoft always first make new versions of their products worse and then (but only with sufficient complaints) repair a part of what was destroyed? And not alone in VS....

I will certainly not install VS 2019 until there's some reason I no longer can use VS 2017. I've updated to VS 2017 last august because I couldn't develop UWP apps with VS 2015 and the W10 version of that moment anymore. It took me 1,5 day to get VS2017 working thanks to the "improved" installer. Can't remember to have found any of the main improvements; e.g. startup time VS was even slower when I started. So in general it's a good idea to postpone Microsoft updates as long as possible.

I also added a reply to the page Robert posted. Hopefully they'll get on this.

It's good to hear that XSharp functions good with VS2019, other than the setback.
I think I can't temper certain colleagues to try VS2019 out.

I am running the latest 16.02 version of VD 2019 Community Edition, and It will not open any X# Sharp Project, nor will it create any news ones, even searching the manual search trick that were reported in this thread.

Replying on #8

Hello Matt,

Two options: 1 Maybe a very simple suggestion - did you actually install XSharp on the VS2019 machine?

I decided to install VS 2019 on a spare laptop and then X#. I could find all X# templates and start a new WPF program. I opened an existing project. I had to set to a higher .Net version, got some Mismatch warnings, even 2 XS9003 Preprocesses Include file not found errors - but my program started! A true miracle on a new VS version.

Second: I have seen this error more than once. Going to a newer VS versions is a bit like participating in a lottery: the chances are high that you lose. I often restarted the project, imported the .PRG and XAML files and applied the settings and includes and then it worked. Also sometimes it helped to open the project instead of the .sln file but you already did so judging from the screenshot.

Finally: maybe this helps you finding the cause:

answers.unrealengine.com/questions/20241...g-visual-studio.html

Dick

Dick,
OT:
Seeing you try to install a "message tree" a la "replying to #8" - if you change the display order, e.g. to show latest posts top (as i did) - the numbering goes havock - ATM "Your" post has #1 here
/OT
Karl

It's working fine for me in VS2019. Did you perhaps install VS2019 after installing X#? Either way, trying running the X# installer again and make sure that VS2019 integration is selected during the install.

fxm - are you running 16.0.2??

I did re-run the X# installer after I upgraded to 16.0.2, but this get this error. I had 2019 RC before full release, but VS said it upgraded from RC to 16.0.0 final, then 16.0.1 then 16.0.2.

I may need to uninstall 16.0.2, and just start the whole process all over again.

FoxProMatt_MattSlay wrote: fxm - are you running 16.0.2??

No, sorry - running 16.1.0 Preview 2.0 which was released yesterday

Replying to #10

Hello Karl,
It's even worse: when I click reply your message #10 has become #9
One would expect a message tree to be a default feature in forums like this. If there are many messages on 1 subject it's hard to see who is replying to whom.
Apart from the emoticons, easier adding a picture and the lay-out options the newsgroup solutions was better in all other respects. It's not the only tech based development which is a step back from the "old fashioned" predecessor.

Dick

Good news... complete uninstall, then re-install to 16.0.2, then reinstall X# now It works again.

Next up, I will upgrade to 16.1.0 Preview 2.0.

Excellent!

FoxProMatt_MattSlay wrote: Next up, I will upgrade to 16.1.0 Preview 2.0.

I plan to do the opposite - uninstall the Preview release and drop back to the official release..

Why roll back?

Are you having trouble?

Hi Dick,

ic2 wrote: It's even worse: when I click reply your message #10 has become #9
One would expect a message tree to be a default feature in forums like this. If there are many messages on 1 subject it's hard to see who is replying to whom.
Apart from the emoticons, easier adding a picture and the lay-out options the newsgroup solutions was better in all other respects. It's not the only tech based development which is a step back from the "old fashioned" predecessor.

Well, you can quote the message you are replying to, this makes it all clear, isn't it in this message?

FoxProMatt_MattSlay wrote: Why roll back?

Are you having trouble?

No problems at all but it's the Preview Release and not recommended for use on production machines.

docs.microsoft.com/en-us/visualstudio/re...elease-notes-preview

This release is not "go-live" and not intended for use on production computers or for creating production code.

fxm - you can have both installed at the same time, and they run separately just fine.

I now have both 16.0.2 and 16.1.0 Preview 2.0 both installed on my machine.