You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Intellisense for a fsx file shows error after changing column names in excel template file.
Repro steps
Create an Excel template file with columns A and B called test.xlsx. Reference the type provider dll in an fsx file. Create the types using the text.xlsx. Write some code using columns A and B
Step A
Change column B to C in the excel file.
Step B
Change the naming of column B to C in the fsx file. Intellisense shows and error for using column C. However, the code can be loaded to the fsi without problems. The only way to be able to correct the intellisense problem is by renaming the test.xlsx to for example test1.xlsx and use that file.
Expected behavior
Intellisense adjusts to the new column C.
Actual behavior
Intellisense keeps refering to column B.
Known workarounds
Renaming the template file and using that as type provider.
Related information
Windows 7
.NET 4
The text was updated successfully, but these errors were encountered:
Description
Intellisense for a fsx file shows error after changing column names in excel template file.
Repro steps
Create an Excel template file with columns A and B called test.xlsx. Reference the type provider dll in an fsx file. Create the types using the text.xlsx. Write some code using columns A and B
Change column B to C in the excel file.
Change the naming of column B to C in the fsx file. Intellisense shows and error for using column C. However, the code can be loaded to the fsi without problems. The only way to be able to correct the intellisense problem is by renaming the test.xlsx to for example test1.xlsx and use that file.
Expected behavior
Intellisense adjusts to the new column C.
Actual behavior
Intellisense keeps refering to column B.
Known workarounds
Renaming the template file and using that as type provider.
Related information
The text was updated successfully, but these errors were encountered: