« first day (2298 days earlier)      last day (35 days later) » 

12:00 AM
> Hi,

I'm not an expert on debug here, but as your issue is 5 days old, I'll try.

Exception is thrown by ExportAsSourceFile what exports your code to a textfile that is then parsed (if I got that correct). As you use RDS I assume a problem with the path RD wants to store that files, but I have to look in code to see what path is used for that.. General advice is to always use the newest RD version, as they usually have lots of improvements. E.g. one new feature is version check on startup
RELOAD!
[rubberduck-vba/Rubberduck] 7 issue comments.
[Minesweeper] Games Played: 118, Bombs Used: 88, Moves Performed: 16032, New Users: 10
> Hi,

I'm not an expert on debug here, but as your issue is 5 days old, I'll try.

Exception is thrown by ExportAsSourceFile what exports your code to a textfile that is then parsed (if I got that correct). As you use RDS I assume a problem with the path RD wants to store that files, but I have to look in code to see what path is used for that. General advice is to always use the newest RD version, as they usually have lots of improvements. E.g. one new feature is version check on startup.
 
12:14 AM
> Hi,

I'm not an expert on debug here, but as your issue is 5 days old, I'll try.

Exception is thrown by ExportAsSourceFile what exports your code to a textfile that is then parsed (if I got that correct). As you use RDS I assume a problem with the path RD wants to store that files, what is %appdata%\local\temp\ Rubberduck. That path needs to be writeable on RDS!
General advice is to always use the newest RD version, as they usually have lots of improvements. E.g. one new feature is ver
> Hi,

I'm not an expert on debug here, but as your issue is 5 days old, I'll try.

Exception is thrown by ExportAsSourceFile what exports your code to a textfile that is then parsed (if I got that correct). As you use RDS I assume a problem with the path RD wants to store that files and that is %appdata%\local\temp\ Rubberduck. That path needs to be writeable on RDS!
General advice is to always use the newest RD version, as they usually have lots of improvements. E.g. one new feature is
 
12:39 AM
> Hi,

I'm not an expert on debug here, but as your issue is 5 days old, I'll try.

Exception is thrown by ExportAsSourceFile what exports your code to a textfile that is then parsed (if I got that correct). As you use RDS I assume a problem with the path RD wants to store that files and that is %LocalAppData%\temp\ Rubberduck. That path needs to be writeable on RDS!
General advice is to always use the newest RD version, as they usually have lots of improvements. E.g. one new feature is v
> Hi,

I'm not an expert on debug here, but as your issue is 5 days old, I'll try.

Exception is thrown by ExportAsSourceFile what exports your code to a textfile that is then parsed (if I got that correct). As you use RDS I assume a problem with the path RD wants to store that files and that is %LocalAppData%\temp\Rubberduck. That path needs to be writeable on RDS!
General advice is to always use the newest RD version, as they usually have lots of improvements. E.g. one new feature is ve
> @Imh0t3b thanks for that reply! You are correct, this should be a permission issue.
> > Hi @msdiniz,
> if I didn't miss any relevant infos, you don't suffer on "Out of memory errors and excessively high memory usage" what this issue is about? Then please create a new issue and add log files.
>
> Some tipps for speedup from the [blog](https://rubberduckvba.wordpress.com/2020/08/22/rubberduck-2-5-1/):
>
> * Disable “run inspections automatically on successful parse”, so that they only run if you explicitly refresh them from the Inspection Results toolwindow;
> * Set inspe
> > Hi @msdiniz,
> if I didn't miss any relevant infos, you don't suffer on "Out of memory errors and excessively high memory usage" what this issue is about? Then please create a new issue and add log files.
>
> Some tipps for speedup from the [blog](https://rubberduckvba.wordpress.com/2020/08/22/rubberduck-2-5-1/):
>
> * Disable “run inspections automatically on successful parse”, so that they only run if you explicitly refresh them from the Inspection Results toolwindow;
> * Set inspe
> > Hi @msdiniz,
> if I didn't miss any relevant infos, you don't suffer on "Out of memory errors and excessively high memory usage" what this issue is about? Then please create a new issue and add log files.
>
> Some tipps for speedup from the [blog](https://rubberduckvba.wordpress.com/2020/08/22/rubberduck-2-5-1/):
>
> * Disable “run inspections automatically on successful parse”, so that they only run if you explicitly refresh them from the Inspection Results toolwindow;
> * Set inspe
 
 
1 hour later…
2:23 AM
> @retailcoder do we handle that as user misconfig (as we have a check for folder exists, but not for is writeable) or should we implement a test for is writeable and use a different folder (e.g. Roaming\temp) if not writeable? I would vote for message on startup to fix that issue and close RD.
> Alternatively, I'm guessing we could prompt the user to supply a folder they have write access to, so that the parser still has a place to export the code files... we should make that folder configurable.
> @msdiniz,

> I though that it was implicit

Don't you read the [blog](https://rubberduckvba.wordpress.com/? Always be explicit (not only on refernves)! ;)

Any reason you don't switch to Office x64, as that solves all "Out Of Memory" issues. Ever tried Ms Access (only as frontend) as that is the easiest way creating form bound to data.
> @msdiniz,

> I though that it was implicit

Don't you read the [blog](https://rubberduckvba.wordpress.com/)? Always be explicit (not only on refernves)! ;)

Any reason you don't switch to Office x64, as that solves all "Out Of Memory" issues. Ever tried Ms Access (only as frontend) as that is the easiest way creating form bound to data.
> @msdiniz,

> I though that it was implicit

Don't you read the [blog](https://rubberduckvba.wordpress.com/)? Always be explicit (not only on references)! ;)

Any reason you don't switch to Office x64, as that solves all "Out Of Memory" issues. Ever tried Ms Access (only as frontend) as that is the easiest way creating form bound to data.
 
3:02 AM
> @msdiniz,

> I though that it was implicit

Don't you read the [blog](https://rubberduckvba.wordpress.com/)? Always be explicit (not only on references)! ;)

Any reason you don't switch to Office x64, as that solves all "Out Of Memory" issues. Ever tried Ms Access (only as frontend) as that is the easiest way creating form bound to data.

> I'm capable to see RB functioning now because of some fine tuning that you RB guys did,

Yes they are great!! One cannot thank them enough!! Tha
> @msdiniz,

> I though that it was implicit

Don't you read the [blog](https://rubberduckvba.wordpress.com/)? Always be explicit (not only on references)! ;)

Any reason you don't switch to Office x64, as that solves all "Out Of Memory" issues. Ever tried Ms Access (only as frontend) as that is the easiest way creating form bound to data.

> I'm capable to see RB functioning now because of some fine tuning that you RB guys did,

Yes they are great!! One cannot thank them enough!! Tha
 
3:22 AM
> Difficulty level of checking write access and showing a file-dialog > difficulty-01-duckling? Maybe a challange for me ( at time I'm stuck on listview TextWrapping #5013)
 
 
9 hours later…
12:26 PM
> @Imh0t3b the core problem is that we might be using that path in a hard-coded way in multiple places. That makes the issue a bit more complex than just checking write-access and getting a new path.

It's not necessarily more difficult, but definitely more work than it might seem at first.
 
1:25 PM
> @Vogel612 more complicated than replacing Path.GetTempPath() with a method that checks the path and requests a new one if not writeable in RUBBERDUCK_TEMP_PATH = Path.Combine(Path.GetTempPath(), "Rubberduck"); in Rubberduck.Resources.ApplicationConstants=
> FWIW, we have the issue #4533 & #4794 because that would be the best place to handle filesystem problems, including lack of write permission & taking configuration values. That might need to expand the existing [`PersistencePathProvider`](https://github.com/rubberduck-vba/Rubberduck/blob/dd68164d6368ff48a0c7dd7bc690bc102a939f86/Rubberduck.SettingsProvider/Persistence/PersistencePathProvider.cs) to provide for temporary path.

It's a bit odd that there can be permission issues with `GetTempPa
> We're not using GetTempPath... the source is exported through the `TempSourceFileHandler`. For the Office-Attached VBE, the implementation is in Rubberduck.VBEditor.VBA and looks as follows:

https://github.com/rubberduck-vba/Rubberduck/blob/8695c05e91cbd9f6ba9dd324c523ac89cf33b331/Rubberduck.VBEditor.VBA/TempSourceFileHandler.cs#L13-L17

At this point we need to check all usages of `RUBBERDUCK_TEMP_PATH` for this issue and replace it with a lazily initialized Path that can be defined in t
 
good lord it's complicated to find things through IoC in the Github interface, and doubly so when your browser has a rendering bug around erasing rectangles...
 
1:53 PM
> That's why I linked the issues; IMPOV, those components have no business fiddling with `System.IO`; that needs to be delegated to a class dedicated to handling the filesystem access in an uniform manner.

BTW, that does actually use `GetTempPath`:
https://github.com/rubberduck-vba/Rubberduck/blob/23039cc5ecda48fb1b8acd4da0d982c9149dab54/Rubberduck.Resources/ApplicationConstants.cs#L10
> @Imh0t3b,
> Don't you read the [blog](https://rubberduckvba.wordpress.com/)? Always be explicit (not only on references)! ;)
Yeah, sorry. I should applied what I've learned the hard way about to be explicit ever on references!

> Any reason you don't switch to Office x64, as that solves all "Out Of Memory" issues. Ever tried Ms Access (only as frontend) as that is the easiest way creating form bound to data.
Well, I'm from a resource-limited country... I still have more then 50% of the ma
> @Imh0t3b,
> Don't you read the [blog](https://rubberduckvba.wordpress.com/)? Always be explicit (not only on references)! ;)

Yeah, sorry. I should applied what I've learned the hard way about to be explicit ever on references!

> Any reason you don't switch to Office x64, as that solves all "Out Of Memory" issues. Ever tried Ms Access (only as frontend) as that is the easiest way creating form bound to data.

Well, I'm from a resource-limited country... I still have more then 50% of th
> @Imh0t3b,
> Don't you read the [blog](https://rubberduckvba.wordpress.com/)? Always be explicit (not only on references)! ;)

Yeah, sorry. I should applied what I've learned the hard way about to be explicit ever on references!

> Any reason you don't switch to Office x64, as that solves all "Out Of Memory" issues. Ever tried Ms Access (only as frontend) as that is the easiest way creating form bound to data.

Well, I'm from a resource-limited country... I still have more than 50% of th
 
2:24 PM
> @Vogel612 more complicated than replacing Path.GetTempPath() with a method that checks the path and requests a new one if not writeable in `RUBBERDUCK_TEMP_PATH github.com/rubberduck-vba/Rubberduck/blob/…
> Seems out of scope for me then ;( But of xourse I don'tneed to worry about no more suitable isues avainle to me. I'll check german translations for completeness and dig somewhat deper into RDs structure.
 
2:56 PM
> @Imh0t3b,
> Don't you read the [blog](https://rubberduckvba.wordpress.com/)? Always be explicit (not only on references)! ;)

Yeah, sorry. I should applied what I've learned the hard way about to be explicit ever on references!

> Any reason you don't switch to Office x64, as that solves all "Out Of Memory" issues. Ever tried Ms Access (only as frontend) as that is the easiest way creating form bound to data.

Well, I'm from a resource-limited country... I still have more than 50% of th
> As I mentioned, our IT department has placed Access on a server and I have to use remote connection to the box. They have it configured so that I very few permissions outside of the folder where I can launch MS Access. I will check on Monday when the IT folks are in the office to see what 'local' folders on the remote server I would have permissions.
> @Imh0t3b,
> Don't you read the [blog](https://rubberduckvba.wordpress.com/)? Always be explicit (not only on references)! ;)

Yeah, sorry. I should applied what I've learned the hard way about to be explicit ever on references!

> Any reason you don't switch to Office x64, as that solves all "Out Of Memory" issues. Ever tried Ms Access (only as frontend) as that is the easiest way creating form bound to data.

Well, I'm from a resource-limited country... I still have more than 50% of th
> @Imh0t3b,
> Don't you read the [blog](https://rubberduckvba.wordpress.com/)? Always be explicit (not only on references)! ;)

Yeah, sorry. I should applied what I've learned the hard way about to be explicit ever on references!

> Any reason you don't switch to Office x64, as that solves all "Out Of Memory" issues. Ever tried Ms Access (only as frontend) as that is the easiest way creating form bound to data.

Well, I'm from a resource-limited country... I still have more than 50% of th
 
 
5 hours later…
7:44 PM
> @Imh0t3b,
> Don't you read the [blog](https://rubberduckvba.wordpress.com/)? Always be explicit (not only on references)! ;)

Yeah, sorry. I should applied what I've learned the hard way about to be explicit ever on references!

> Any reason you don't switch to Office x64, as that solves all "Out Of Memory" issues. Ever tried Ms Access (only as frontend) as that is the easiest way creating form bound to data.

Well, I'm from a resource-limited country... I still have more than 50% of th
 
 
3 hours later…
10:37 PM
 
 
1 hour later…
11:42 PM
> You are delivering the best code that you can deliver, given what you know now.
From holub.com/technical-debt. I really like how that's worded.
2
 

« first day (2298 days earlier)      last day (35 days later) »