Ok, this post appeared, so I'll add more detail.

After the crash, the project file is left permanently damaged. It will open, but TWS loses the PROJECT, BUILD, DEBUG, DATA LOADER, and TEST menu items. Moving the caret around the editor is sluggish, scrolling through code is sluggish in all files, not just the one that was being edited when TWS crashed. The mapping scrollbar redraws very slowly on a 941 line file. Prior to the crash it would draw near instantly.

Rebooting my machine did not clear up this issue. I tried opening the Project directly rather than the Solution, and that does not help.

If I start a second instance of TWS, and open a project that has not yet experienced one of these crashes, TWS works fine.

Apparently your Bug Report system cannot handle html/apex pasted into a HTML code sample. Not sure how to give you the information I tried to give above. Basically removing the "<" before "apex:outputfield" will sometimes cause TWS to crash. Same with removing the "<" at the start of a comment marker in a .COMPONENT file

The code I am editing is inside of an HTML table if that helps track down the issue

TWS is unusable now for editing code with Spire R2 for me. Almost every time I type the character "<" while editing a .COMPONENT file, TWS will crash. I have to type what I want in another editor, and paste it into TWS. I have an 8 line simple example file:

(I put comment markers around the code I pasted in, as the bug report page doesn't seem to like Apex code pasted in, and that doesn't work, so I can't supply sample code)

I do a clean pull of all files from Salesforce to a new directory, open the above file. Nothing special about the code. If I insert a new blank line anywhere in the file, and type the "<" character, TWS immediately crashes.

If I paste in a "<" all by itself, the crash does not occur, only if I type in the "<" (which I need to do at least once on every line).

Hi gtasker,

Thank you for letting us know about this issue. Also thank you for going through the forum issues and providing us all this information!

Right now it is unclear to us what can be the reason of such behavior, but we are already working on reproducing and/or analyzing the issue and it's possible reasons.

In order for us to get some more background can you please answer some questions:

1. Was this issue actual for you on R1 version?


2. Can you remember after what actions/changes this issue started to occur?


3. Is it occuring for all of the visualforce components, or only for some of them?


4. If the issue occurs on all components - it would be greate if you could try creating/opening any other project and working with components there. Is behavior the same?


5. If the issue occurs only on one/some of the components - can you think of something specific about that files?


6. Is the issue also occurs for Visualforce pages?


7. Can you please send us a bug report via The Welkin Suite itself - You can find this option in the Main Menu -> Help -> Report a Bug. Please enter your email for our feedback and enable the 'Attach Log File' checkbox. This way we will get you Activity Log file that will help in our investigation process.
   

   
   
   

As we are not yet aware about the root cause of the issue the only workaround I can propose you right now is to right-click on the component file, select Open With and select Source Code (Text) Editor and then click "Set as Default" button. In this case Visualforce components would be opened as a plain text without any syntax highlighting or any functionality.

We will keep you updated about the investigation process.



Thank you,

Vladimir

Was this issue actual for you on R1 version?

I had seen this behavior in the last Beta, but it had only happened a few times, and I was not able to reproduce it. I do not recall it happening in R1, but I only had R1 installed for one day before installing R2, and I had limited work that day on .COMPONENT files.

1. 
   

   Can you remember after what actions/changes this issue started to occur?

   
   

I installed R2, I created a new Solution, pulled everything from Salesforce into a new folder, and it immediately happens. I can duplicate this every time.

1. 
   

   Is it occuring for all of the visualforce components, or only for some of them?

   
   

It happens for every component file I have, from a larger ~1000 line file to an 8 line file that just displays a single label and image

1. 
   

   If the issue occurs on all components - it would be greate if you could try creating/opening any other project and working with components there. Is behavior the same?

   
   

I have created a completely different project, from a different Org, that has none of the code that exists on the original Org I was using. I have no components in this project, but I can confirm the problem also occurs in this project with all VF pages I tested.

1. 
   

   If the issue occurs only on one/some of the components - can you think of something specific about that files?

   
   

It happens on all components that I have tried (7 now). I have 36 component files, I have not tried them all

1. 
   

   Is the issue also occurs for Visualforce pages?

   
   

Yes, the same problem occurs with VF pages. For the work I have been doing, it has all been in the COMPONENTS so I hadn't thought to try VF pages, but I just tried a VF page now, and the crash happens there also.

I just started a new project, all I pulled down from my Sandbox org was the Objects. I added a new VF page to the project. The initial code looked like this (I replaced the angle brackets with square brackets in this bug report, since the forum cannot handle tags in the code):

[apex:page ][/apex:page]

I inserted a blank line between the two tags and pressed "<" and TWS crashed.

I just uninstalled TWS Spire R2 (note I did not uninstall my personal settings). Reinstalled Spire R2 to my Windows 10 machine, rebooted.

I created a new Salesforce Project, logged in to my sandbox Org, and pulled down nothing from the server. Totally new project, with no code, objects, or anything.

I then right clicked the project name in the Solution Explorer, added a VF page. I inserted a blank line between the tags that TWS started me off with, pressed "<" and TWS crashes.

This eliminates all of my code from being part of the cause of the crash.

I have duplicated this with Orgs on cs83 and cs87. I have tried with both the Unlimited Edition and Enterprise Edition

Hi Gtasker,



Thank you for all the details. We appreciate this greatly!

Our developers have investigated the issues you are faced with and the reason for this behavior of TWS can be the incorrect installation of Microsoft Visual Studio Shell (Isolated).

I kindly ask you to send us a bug report directly from the IDE as Vladimir wrote: Main Menu -> Help -> Report a Bug. We will get your log files which can help us to make sure of the Isoshell is the reason for your issues or get the information about another reason.

In case if the issues are caused by the Isoshel installation, this will be necessary to uninstall Microsoft Visual Studio Shell (Isolated) and The Welkin Suite IDE, and then repeat the TWS installation.



Thank you for your collaboration.

Best Regards,

Kate

Done

Thank you for the bug report with the attached log files.

Our assumption related to the reason for your issue is confirmed. This was caused by the absent application file in the Microsoft Visual Studio Shell (Isolated).



Here are the steps that can help you to solve the issue:

1) please uninstall The Welkin Suite IDE;

2) please uninstall Microsoft Visual Studio Shell (Isolated) in the Programs and Features list also;

3) after this, this is necessary to reboot your machine;

4) please install the welkin Suite IDE again.



I kindly ask you to let us know if the issues are reproduced for you after these steps.

Our developers will investigate this case to avoid this in future.



Best Regards,

Kate